As a lot of other maven users (I have read many threads on this topic), I try to limit the places where version numbers are explicitely set. I have uploaded http://rapidshare.de/files/48725253/test-mvn.zip.html here a small test case to illustrate what i say below.
My multiproject P1 holds a single module A. P1 pom declares a property P1.version, which is used to set the artifact version of P1, the artifact version of A, the parent version of A. I can build P1, as A finds its parent from the file system. I can no longer build A alone, but I accomodate with that. A project P0 uses A. P0 declares the P1.version property, and declares A as a dependency. I cannot build P0, as A cannot find its parent. It seems that the P1.version definition from P0 is not known or interpreted when maven resolves the parent section of A. Of course, if P0 and P1 are defined as modules of a super project, then I can build the super project. Is there any rationale for this behaviour ? Thanks for your comments. -- View this message in context: http://old.nabble.com/versioning-using-properties-tp26478836p26478836.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
