versions-maven-plugin.... some of the mojo's we're (or I'm) intending on putting in are not there yet.
The first mojo to look at is: update-properties (you'd be wanting the version from 1.0-alpha-3-SNAPSHOT btw) This picks up any dependencies who's version comes from a property and allows picking the newest version available and using that. Two other goals which I'm planning are use-releases (will scan your project for any dependencies which are -SNAPSHOT and have the corresponding release version available) use-snapshots (will scan your project for any dependencies which have a newer -SNAPSHOT available and use that) note that use-releases is safer than use-snapshots as removing the -SNAPSHOT is unambiguous, but adding a -SNAPSHOT is more difficult... 1.0.3 => 1.0.4-SNAPSHOT, or 1.1.0-SNAPSHOT, or 2.0.0-SNAPSHOT what one should we look for, and when should we use it 2009/3/30 <[email protected]> > Hi, > > we have a large system, containing separate software modules (backend.ear, > ui.war, services.war and so on....) > > During developement, we use snapshot dependencies to reference the other > modules. > So a version of the whole system can be build by "one click" on our > buildsystem, which than just deploys a new snapshot version and all is > fine. > > During release (one times a week) we need first to release the modules one > by one - actually per hand, swap dependency versions and so on, > than swap dependency versions back to next snapshot for the develeopement > of next week and so on. > This is very error-prone and time consuming. > > What´s the way to do this more efficient? Always build the whole system as > one "multimodule" build? > Is there a plugin that automatically can change dependency versions in > pom.xml if there are newer versions available? > > Thanx, > > torsten
