> The jar tasks work as expected (see artifact versions in build/libs).
> However, the upload tasks seem to treat their configuration as a unit, and
> hence use the project version instead of individual artifact versions.
> Maybe we should make it possible to set a version for each upload task.
> Please create an issue describing your use case.
>
> Will do.
>
> Meanwhile, you should be able to work around this by changing the global
> version just before the upload task runs. To be on the safe side, I
> recommend to change the version back at the end of the task.
>
> projectVersion = "1.0-SNAPSHOT"
> version = projectVersion
>
> uploadShared.doFirst { project.version = "3.9" }
> uploadShared.doLast { project.version = projectVersion }
>
> Thanks for the workaround.
>
> --
> Peter Niederwieser
> Developer, Gradle
> http://www.gradle.org
> Trainer & Consultant, Gradle Inc.
> http://www.gradle.biz
> Creator, Spock Framework
> http://spockframework.org
>
>
>
>
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Create-an-artifact-with-a-different-version-number-as-the-main-project-tp3374437p3375893.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
