[
https://issues.apache.org/jira/browse/MNG-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678805#comment-17678805
]
ASF GitHub Bot commented on MNG-7669:
-------------------------------------
laeubi opened a new pull request, #964:
URL: https://github.com/apache/maven/pull/964
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.
This adds a new default mapping so this type can be used smoothly in maven.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MNG) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MNG-XXX] SUMMARY`,
where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA
issue.
- [x] Also format the first line of the commit message like `[MNG-XXX]
SUMMARY`.
Best practice is to use the JIRA issue title in both the pull request
title and in the first line of the commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> 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)
