Multi-module build order and circular dependencies

[Guillaume Lederrey <gu...@gmail.com>]

Hello

I'm in the process of converting a few projects to Maven. Most of
those projects have indirect circular dependencies between their
modules. If I run maven on the main pom, it fails because it mixes up
the dependencies and tries to compile them in the wrong order. If I
run maven on each of the modules by hand, in the right order, than it
works fine. Once the modules are installed in the local maven
repository, I can compile by running maven on the main pom. Only the
first run of maven is problematic.

The problem arises when trying to do a release. As part of the release
process, maven compile the project, after having updated the version
numbers. In my case, it fails. Of course, I can manually run maven on
each project as part of my release process, but I'd like the process
to be fully automated.

I'm thinking at adding an "exec" preparationGoal to the release
plugin. This goal would execute "mvn -f module1/pom.xml" on the right
modules. Problem : I have to run maven on more than one module. How
can I configure multiple instances of the exec plugin ?

Or is there an obvious, or easier way to achieve my goal ?

Refactoring is sadly not an option for the moment.

Thanks for your help !



-- 
Jabber : gehel@amessage.ch
Skype : Guillaume.Lederrey
Projects :
* http://rwanda.wordpress.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org