This is pretty tricky, because the versions are selected based on the
interpolated POM, and it's possible (but unlikely) something like
this might happen:
project.version=1.0-alpha-1-SNAPSHOT
module1: ${project.version}
module2: ${project.version}
and then we select:
module1: 1.0-alpha-1
mod
Please see:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/plexus/security/plexus-security/1.0-alpha-8/plexus-security-1.0-alpha-8.pom
Its clear that the release manager failed to update the expression
definition of the dependency versions. Fixing this bug will be easy if
only the