I am looking for some advice on how to properly structure my build. I have a multi-project build with several layers of pom abstraction, the ultimate parent being "maven-build" project. The maven-build pom.xml resides in root directory where all of my subprojects reside. Currently, the maven-build project builds 5 modules, each of those modules building 1 or more modules. In addition, I have defined a dependencyManagement section, common plugins like clover, javadoc, surefire, etc.
The problem that I am having is when I add something new to the dependencyManagement section of maven-build (i.e commons-logging-1.0.jar) and to a project that uses that dependency my build fails because the version is specificed in the project that uses it. If I comment out the modules in the maven-build pom.xml and do a clean install, the uncomment them it works. Basically what is happening is that the maven-build pom.xml is not in the local repo until it has been build (and all modules are built). I am thinking that the best way to deal with this is to put a profile tag around the modules section in the maven-build pom.xml file but I am not sure if this is the best way to approach things. It is kinda of a chicken and egg scenario. I want the power of inheriting dependencies from dependencyManagement as well as plugin configurations, but I have to have a better way to deal with updates to the maven-build pom.xml file. Any suggestions would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/Parent-pom-file-usage-tf3149151s177.html#a8730361 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
