[GRADLE-1201] Add support for deploying metadata artifacts using the maven plugin Created: 02/Nov/10 Updated: 10/Feb/17 Resolved: 10/Feb/17
At this point you can only deploy one main artifact and several artifacts with classifiers using the maven plugin. This means that metadata files like signed artifacts (name example: groovycsv-0.2.jar.asc) can't be uploaded using the maven plugin.
What I gather from the sources is that there will have to be a codechange in gradle to support some kind of metadata artifact, but more importantly, the deployer will have to be changed to support these new artifacts.
This feature is very important because the lack of it means that it's not possible using Gradle's maven plugin to deploy artifacts to Nexus OSS Repo for syncronization with Maven Central.
|Comment by Adam Murdoch [ 03/Nov/10 ]|
This is partially fixed in the master branch. You can now add extra artifacts without classifiers to be uploaded.
There's no support in the DSL, yet, so I've left this issue open.
|Comment by Leonard Axelsson [ 05/Nov/10 ]|
Thanks a lot!
|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:
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.