uploadArchives doesn't use custom versioning scheme

(Michael Larsen) #1

I have a plugin to implement a custom versioning scheme, nearly identical to the suggestion in section of the docs. Projects apply the plugin and then declare dependencies as suggested ‘group:name:default’. The plugin replaces ‘default’ with the correct version as determined by the logic in the plugin. This all works great.

The problem is that when I run uploadArchives, using the mavenDeployer, the resulting pom file has a version of ‘default’ for all of the dependencies.

Is there a way to have the uploadArchives task use the version resolved by the custom version scheme?

Custom plugin - dependencies version update
(Andreas Nyberg) #2

I just hit this showstopper myself using ivy-publish with 1.7-rc-1. It seems DependencyResolveDetails useVersion only refers to using the indicated version for the resolution but not actually substituting it throughout.