Hi,
1- In my trunk, I've got a project like this
Parent 1.1.0-SNAPSHOT
|-Project1 0.0.5-SNAPSHOT (depends on Project2 0.0.3-SNAPSHOT)
|-Project2 0.0.3-SNAPSHOT
2- After a release of the parent 1.1.0-SNAPSHOT I would like ti have in my
tag:
Parent 1.1.0
|-Project1 0.0.5 (depends on Project2 0.0.3)
|-Project2 0.0.3
And in my trunk
Parent 1.2.0-SNAPSHOT
|-Project1 0.0.6-SNAPSHOT (depends on Project2 0.0.4-SNAPSHOT)
|-Project2 0.0.4-SNAPSHOT
But it seems it's not possible and de dependencies are not well managed at
the end I've:
Parent 1.1.0
|-Project1 0.0.5 (depends on Project2 0.0.3-SNAPSHOT)
|-Project2 0.0.3
And in my trunk
Parent 1.2.0-SNAPSHOT
|-Project1 0.0.6-SNAPSHOT (depends on Project2 0.0.3-SNAPSHOT)
|-Project2 0.0.4-SNAPSHOT
I'm a new maven user, in the example I didn't used the dependency manager
for the version in the parent, I declare the dependence version in the
Project1 - pom.xml. I read in the BetterBuilds with Maven to used the
dependency manager with ${project.version} for the entire child version but
it's not what I want. I want each child to have is own life (release it
independently if needed)
For the moment, I defined properties in the parent-pom.xml which correspond
to version I mean:
<properties>
<Project1.version>0.0.5-SNAPSHOT</Project1.version>
<Project2.version>0.0.3-SNAPSHOT</Project2.version>
</properties>
Then I used ${xxx.version} in my project, I've to modify these properties
before a release but at least at the end I've what I want.
I'm pretty sure it's not the best practices but I didn't find a solution to
solve the version increment dependence.
Thanks in advance for your answer
Lionel
--
View this message in context:
http://n2.nabble.com/Best-Practices-Maven-release-plugin-multimodule-with-module-dependencies---tp1397646p1397646.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]
