I have a multi-module project with two levels of transitive
dependencies like this :
pom.xml
- module1 - project1 depends on project2
- module2 - project2 depends on project3
- module3 - project3
in my parent pom I specify in my dependency management section my
modules dependencies with ${project.version} like specified in maven
book.
My parent pom version is 1.0-SNAPSHOT.
My problem is that my project1 dependencies fail. My understanding of
the problem is that project2 replace ${project.version} not with
1.0-SNAPSHOT but with its own build version number
"1.0-20060721.110913-11". As project3 was not build at the same time.
Maven can't find project3-1.0-20060721.110913-11.pom.
If I replace ${project.version} in my dependency management with
1.0-SNAPSHOT everything is ok.
The problem is that the release plugin does not replace this number
with the next SNAPSHOT version.
Is this a bug or something normal ? Is there any best practice in my case ?
Thanx
Seb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
