[GRADLE-1382] Unable to set the version of an artifact uploaded to a repository Created: 08/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Luciano Fiandesio Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Given the following Gradle file:

build.gradle
============================
apply plugin: 'java'
version = '1.0-SNAPSHOT'
group = 'com.some'

configurations {
shared
}

task sharedJar(type: Jar) {
baseName = 'shared'
version = "3.9"
...
}

artifacts {
shared sharedJar
}

uploadShared {
uploadDescriptor = false
repositories

{ add project.repositories.localRepository }


}
============================

When I run "gradle uploadShared" a jar is created in the proper folder of my "localRepository". The file name is "shared-1.0-SNAPSHOT.jar" but it should be shared-3.9.jar

More info here: http://gradle.1045684.n5.nabble.com/Create-an-artifact-with-a-different-version-number-as-the-main-project-td3374437.html



 Comments   
Comment by Jordan Grant [ 22/Mar/13 ]

I would like to see this functionality as well. I think that the version is not the only thing ignored by the upload task. When we explicitly set the archiveName property of a jar, it is built successfully, but is renamed to the default archiveName upon upload.

Given:

build.gradle
apply plugin: 'java' 
version = '1.0-SNAPSHOT' 
group = 'com.some'

configurations { 
   shared 
}
task sharedJar(type: Jar) { 
   archiveName = "common-resources.jar"
... 
}

artifacts { 
   shared sharedJar 
}

uploadShared { 
   repositories { add project.repositories.localRepository } 
} 

The uploaded file name is "shared-1.0-SNAPSHOT.jar" but it should be "common-resources.jar"

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 11:54:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.