[GRADLE-2173] Artifact not found when maven classifier is hk2-jar Created: 14/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-9
Fix Version/s: None

Type: Improvement
Reporter: Ståle Undheim Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Components package for glassfish has their classifier set to hk2-jar, which is just a jar file with extra osgi information for glassfish hk2 kernel.

This issue is really the same as GRADLE-2076

The fix is the same, in GradlePomModuleDescriptorBuilder add hk2-jar to the list of JAR_PACKAGINGS.

An alternative solution, would be to add some fallback extensions to check, when an artifact is not found with the same extension as the packaging. Or allow mappings to be added in the build script.

Comment by Ståle Undheim [ 14/Mar/12 ]

Added a fix on github that can be merged in:


Comment by Adam Murdoch [ 19/Aug/12 ]

This should be fixed in Gradle 1.1. Can you test this out and let us know if the problem is fixed for you? Thanks.

Comment by Ståle Undheim [ 20/Aug/12 ]

Works fine for me. It also works for orbit files in the latest version off jetty.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:14:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.