On Apr 18, 2008, at 2:43 PM, Ruchith Fernando wrote:
Most of the WS projects seems to maintain the structure of a modules dir (example: axis2, rampart, commons, sandesha2). I personally would like to stick to the same pattern.
Right, I agree -- we want to obey whatever patterns are in use, so I'm fine with that.
In rampart we maintain the versions at the pom.xml at above the modules dir and use that as the parent pom of the modules ... but I don't mind using a seperate parent module if that is the better approach in the maven2 way of things :-)
Yeah, I've been around and around with maven on this. I think there's a chicken-and-egg problem -- if you want to use the root POM as the parent, /and/ you want to use the root POM to drive the build of the modules (you didn't say this, but I'm assuming that's how it works), then you get into a situation where you need to have installed the root in order to build, since the project leaves will need to find their parents in maven (local or remote repo). Better to have a parent module, which gets kicked off and installs first in the list of projects.
Of course, this means the root POM can't have the project parent POM as it's parent, but we should be able to work with that. The root POM just becomes a kind of maven "shell".
-Fred --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
