[GRADLE-2412] Unable to alter the name of the artifact if publishing via Ivy Created: 01/Aug/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.1
Fix Version/s: None

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 9


 Description   

The name used for the artifact for publishing via Ivy is mapped to project.name, which is immutable and may not be what the user wants.



 Comments   
Comment by Luke Daley [ 01/Aug/12 ]

This is happening @ ProjectInternalServiceRegistry#createDependencyMetaDataProvider

Comment by Adam Murdoch [ 03/Sep/13 ]

This is fixed in the new `ivy-publish` plugin. It is not fixed for the old `uploadArchives` task.

Comment by Baiyan Huang [ 07/Nov/13 ]

ivy-publish name change doesn't scale - I would still prefer to change the project name, and then let ivypublish follow it.

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:21:12 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.