[jira] [Commented] (MNG-7669) Add artifact type for Tycho

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678813#comment-17678813 ] 

ASF GitHub Bot commented on MNG-7669:
-------------------------------------

laeubi commented on PR #964:
URL: https://github.com/apache/maven/pull/964#issuecomment-1397301706

   > I think this should be master first.
   
   I can create one for master as well, but if its not accepted for 3.9 it does not make much sense to port it (as master is a bit different one can't just cherry pick it from there).
   
   > What about lifecycles?
   
   The problem only arise if maven tries to resolve an artifact, lifecycle is not affected.




> Add artifact type for Tycho
> ---------------------------
>
>                 Key: MNG-7669
>                 URL: https://issues.apache.org/jira/browse/MNG-7669
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Christoph Läubrich
>            Priority: Major
>
> Since a while Tycho is going more and more "maven-like" so today even more Tycho artifacts approaching at maven-central.
> In some circumstances this leads to strange problems, because Dependencies have a *type* (usually the packaging type) but artifacts have an *extension* (where different packaging types often map to the same extension), and maven only includes a few mappings by default users currently need to enable an extension so that this works.
> I therefore like to gently ask adding a mapping to the default maven supported list that maps tycho-plugin (*type*) -> jar (*extension*).
> It would be great if it could be included in maven 3.9.0 (would be a good argument to move on to newer maven version for our users!)!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)