# uploadArchives doesn't use custom versioning scheme

**URL:** <https://discuss.gradle.org/t/uploadarchives-doesnt-use-custom-versioning-scheme/1073>\
**Category:** Old Forum Archive\
**Created:** [June 6, 2013, 1:59am UTC](https://discuss.gradle.org/t/uploadarchives-doesnt-use-custom-versioning-scheme/1073 "2013-06-06T01:59:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Larsen](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/michael_larsen/32/309_2.png) [@Michael\_Larsen](https://discuss.gradle.org/u/Michael_Larsen)\
**Post date:** [June 6, 2013, 1:59am UTC](https://discuss.gradle.org/t/uploadarchives-doesnt-use-custom-versioning-scheme/1073/1 "2013-06-06T01:59:00Z")

</div>

I have a plugin to implement a custom versioning scheme, nearly identical to the suggestion in section 49.8.2.2 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?

---

<div class="post-metadata">

**Author:** ![middlewareman](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/middlewareman/32/78_2.png) [@middlewareman](https://discuss.gradle.org/u/middlewareman)\
**Post date:** [July 8, 2013, 5:30pm UTC](https://discuss.gradle.org/t/uploadarchives-doesnt-use-custom-versioning-scheme/1073/2 "2013-07-08T17:30:00Z")

</div>

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.