Hi everyone,
It seems that I've got some missunderstanding of the maven2 mechanisms,
and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml *1
|--- module1
| |--- pom.xml *2
|--- module2
| |--- pom.xml -> depends on module1
...
*1 -> packaging: pom, lists submodules in <modules>,
<version>1.12-SNAPSHOT</version>, <dependencyManagement> entries for the
submodules using <version>${project.version}</version>
*2 -> packaging jar or whatever, <parent> references the above pom, no
<version> tag for project itself (inherited), dependencies listed
without <version> tags (-> dependencyManagement)
When building the project during development I executed "mvn install" in
the root folder, and due to the ordering of the modules in the parent
pom maven builds one module after the other, installs it in the local
repository, and uses it to build the other modules. Everything's fine
until here.
Now when I use the maven-release plugin and execute release:prepare, the
plugin changes the version numbers from say "1.12-SNAPSHOT" to "1.12"
and then executes the build, but only up to the "integration-test"
lifecycle phase. "module1" in my example builds successfully, but the
build of "module2" fails since "module1-1.12.jar" is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
