Peter, use the <dependencyManagement> section in the parent pom to pin down the versions of the single child modules.
LieGrue, strub --- Peter Niederwieser <[email protected]> schrieb am Do, 19.11.2009: > Von: Peter Niederwieser <[email protected]> > Betreff: Problem with maven-release-plugin > An: [email protected] > Datum: Donnerstag, 19. November 2009, 11:46 > > In my multi-module project, I have a Maven plugin A and a > module B that uses > version ${project.version} of A (all modules have the same > version number). > release:prepare changes version A from 0.3-SNAPSHOT to 0.3, > but then fails > while processing B because it cannot find version 0.3 of A. > Any ideas how to > solve this problem? > > Cheers, > Peter > -- > View this message in context: > http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html > Sent from the Maven - Users mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
