Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
FIX - packaging.type property is breaking various build systems (sbt, gradle, ivy, etc.) #576
you'd need to sign the OCA to be able to contribute, see http://www.oracle.com/technetwork/community/oca-486395.html
also, proposed change is not a proper fix, if you'd evaluate the pom file more carefuly, you'd notice that the packaging type for jdk8 and older is
I'm not sure whether I stated this only in private messages with other involved people, but let me state this again - I'm really sorry this causes issues for ivy and gradle users, but the issue is not in this pom file. It is in the way how ivy/gradle consumes maven artifacts. Seems like authors of maven plugins choose to evaluate pom files DIFFERENTLY than maven and this is a price. I would suggest to file a bug or pull request against gradle maven plugin (and I believe Ivy just reuses the same code).
JAX-RS pom file is ok from pom file spec side - it is perfectly usable from maven.
I'm closing this PR for now.
I'm happy to produce valid maven artifact. Please think about the consequences - what if ivy maven parser at some point break so bad that it won't be able to use from pom files at all - will you then "ask" everyone to stop using maven properties?
I would suggest that you could spend your energy to fixing the issue on ivy side. And thanks for nice words about me, hope you are feeling better now.
I guess one of the reason why people got so angry here is you are closing related tickets (#571, #572, #576, etc.) so quickly and giving an wrong impression that this problem is already solved while it is not solved at all for these people. By reading these related tickets, we can see you have no intention to solve this issue in your side, and we feel totally rejected.
For people suffering from this issue, I would like to leave some pointers:
This was referenced
Feb 10, 2018
FWIW - this got reported in Ivy issue tracker recently. A potential fix has been made in Ivy upstream and the nightly build of Ivy can be tested to make sure this works for those running into this issue in Ivy. Details on how to get the Ivy nightly build is available in the linked JIRA.