maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: continuous releasing: versions:set and/or release:update-version to release an aggregator project
Date Tue, 30 Jul 2013 15:25:34 GMT
Our solution was to stop synchronizing release versions of dependencies.

We were perfectly happy using software from third parties (Apache, 
Spring, etc.) with different versions and ceased to see any reason why 
version 1.10 of the WAR file could not depend on version 1.8 of one of 
our jar files if, in fact, 1.8 was the correct code for 1.10 of our release.

Once we got over the block in our minds, it worked very well.

As a side benefit, we could also quickly see what modules had actually 
changed in each release. If the jar had a 1.10.x version, then it had 
changed; if it was 1.9, then the new release had not required a change 
in that part of the code.

We had 80+ projects making up the application so the reduction in 
workload was appreciated.

It also made it easier to understand the scope of a new release since we 
took an hour at the start of the release cycle and identified the affect 
expected on each module so that I had a pretty good idea about the work 
that was going to be required and the number of project tasks that were 
about to start up.


On 30/07/2013 11:10 AM, Nestor Urquiza wrote:
> Hi guys,
> We use two aggregator projects to release two WAR applications which have
> some shared JAR projects.
> This aggregators are not parents. Strictly speaking the JAR projects do not
> reference back the aggregators.
> As a developer I would like to set a release version not only for the
> aggregator but for all modules it references.
> It looks like the below command will only change the version for the
> aggregator project. Apparently the only way to make the modules change
> their version as well will be to make the aggregator a real parent. This
> would demand us having really two parents for certain JARS while not for
> others. Definitely inheritance is not the way to go but aggregation. This
> command will not fail with an ERROR but the modules will not get updated.
> <pre>
> mvn clean install versions:set -DnewVersion=2.12345678.0
> </pre>
> It looks like the below command is not working:
> <pre>
> mvn -U release:update-versions -DdevelopmentVersion=2.12345679.0
> </pre>
> As I get:
> Required goal not found: release:update-versions in
> org.apache.maven.plugins:maven-release-plugin:2.0-beta-8
> I have found some archives about the subject but no real solution to this
> problem so far.
> Thanks in advance,
> - Nestor Urquiza

Ron Wheeler
Artifact Software Inc
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message