[GRADLE-2134] When using the "classifier" attribute on an Archive task, gradle will not upload the POM to a maven repo and does not replace SNAPSHOT with a timestamp version number. Created: 29/Feb/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-8 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Grant | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 6 |
Attachments: | build.gradle |
Description |
A simple project which creates just a tar/jar/zip from some files and sets the classifier to "dist". (See attached build.gradle). "gradle tasks" no longer displays the "install" task and invoking the "install" tasks gives a "Task not found" error. Removing the classifier specification from the ArchiveTask definition resolves the problem. The same behavior is displayed if the classifier is instead added in the artifacts.archives specification: artifacts { } An extended discussion of this issue can be found here: http://forums.gradle.org/gradle/topics/pom_doesnt_upload |
Comments |
Comment by Scott Palmer [ 29/Feb/12 ] |
duplicate of |
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. |