Allow release:prepare to rewrite the versions 89/4689/1 controller-bulk-release-prepare-only-16 controller-bulk-release-prepare-only-17 controller-bulk-release-prepare-only-18 jenkins-controller-bulk-release-prepare-only-16 jenkins-controller-bulk-release-prepare-only-17 jenkins-controller-bulk-release-prepare-only-18
authorGiovanni Meo <gmeo@cisco.com>
Fri, 24 Jan 2014 10:03:55 +0000 (11:03 +0100)
committerGiovanni Meo <gmeo@cisco.com>
Fri, 24 Jan 2014 10:03:55 +0000 (11:03 +0100)
commit187eb5b18054c76d7663a6ce4ce0a9aefc7e7c3f
treebdc38b305ff0b4946484be6cfdd74f042e374e25
parent350623353a4a170a9b884c6675eaa091a7e38705
Allow release:prepare to rewrite the versions

- If an artifact has a version number defined in a different POM the
release process doesn't try to rewrite the variable in the other pom
file, that is because that may have a cascaded effect on otehr poms
file, so the possible fixes are:
- avoid the global variables as version numbers
- use dependencyManagement section to avoid duplications also
for the project artifacts.
The last option is by far more elegant and functional and is
implemented in this patch.

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
commons/code-parent/pom.xml
commons/parent/pom.xml
mappingservice/api/pom.xml
mappingservice/config/pom.xml
mappingservice/implementation/pom.xml
mappingservice/northbound/pom.xml
mappingservice/pom.xml
mappingservice/southbound/pom.xml