On 9/30/05, Saleem Shafi <[EMAIL PROTECTED]> wrote: > i got the impression that i could reference the pom.xml in app from > the webapp/pom.xml using the <relativePath/> element, but i'm having > trouble getting the app/pom.xml to recognize webapp as a module since > it's embedded in client.
In this structure you have two choices: - inherit from app, use relativePath so it can be found (but still must give g/a/v) - have a client pom that inherits from app, and have each client module inherit from client. Am I understanding correctly here? > on a related note, just questioning the purpose of the whole parent > project notion, i understood from Maven1 and the reactor that the > purpose of a parent project was mainly to allow closely-related > projects to build together rather than having to rely on installed > artifacts.. well, that didn't work in m1, but it does in m2 :) The parent notion is solely for inheritence - ie sharing of metadata among projects. This is different to dependencies (more like composition in OO terms, you don't actually take on their properties but you can use them). <modules> ios the reactor and determines what gets built. Usually, this is symmetrical to <parent/>, but not necessarily. > My question is, if > that's the case, why not just introduce a new revision type to the > existing dependency concept that allows you to specify that you want > the latest code for a particular project built fresh? That's been thought of. I don't think it is in JIRA yet, but you are welcome to file it. It's certainly a mode we'd like to support. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
