The problem is version ranges AFAIK, 3.4.3-SNAPSHOT is newer than 3.4.3-1... but check
http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#132 for the parsing and http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#50 for the sorting rules. With version ranges, the latest one will win. If you are aiming to release 3.4.3-1, you should be doing that from 3.4.3-1-SNAPSHOT AFAIK -Stephen On Wed, Jul 30, 2008 at 7:51 AM, Baeriswyl Kuno - Extern (IT-BA-MV) <[EMAIL PROTECTED]> wrote: > Hello! > > I'm thinking about how to define a release process with maven release > plugin. Our system consists of about 20 cascaded subsystems, each managed by > a separate subversion repository. It should be possible to separatly release > and version them. However, I also need to release the whole system at once. > This task is quite time-consuming, therefore, I'd like to automate as much > as possible. > > I've played arround with the release plugin and stated that I'd like to get > more control for the versions. > > For instance, the default behavior would be to release subsystem A from > 3.4.3-SNAPSHOT to 3.4.3 and continue with developer version 3.4.4-SNAPSHOT. > However, I'd liked to release A from 3.4.3-SNAPSHOT to 3.4.3-1 and continue > with 3.4.3-SNAPSHOT. This way I could eventually release 3.4.3-2 without > need to change the developers version for all subsystems that depend on A. > > Does anybody have experiences controlling versions this way? > > Thanks for your kindly help. > > > Kuno > > > > >
