Hi Arnaud, Thanks for the info. I'm playing with the versions plugin: hopefully that way I wont have to bring scm (release plugin) into the mix in order to address this issue.
Babak 2010/10/26 Arnaud Héritier <[email protected]>: >> >> On Tue, Oct 26, 2010 at 21:00, Arnaud bourree >> <[email protected]>wrote: >> >>> 2010/10/26 Babak Farhang <[email protected]>: >>>> Hi everyone, >>>> >>>> I have a nested, multi-module project in which every module's pom >>>> inherits from a root pom. I'd like to find a way to avoid duplicating >>>> the parent pom version number in every submodule. The aim is to keep >>>> the version number for these submodules in sync with one another, from >>>> one release to the next. Here's a strategy I've tried using >>>> profiles.xml that doesn't quite work. > > It is impossible for now. > It is forbidden/not recommended to use properties in GAV > (GroupId/ArtifactId/Version) > The minimum you can do now is to set the version in the parent pom and in > each child in the parent section > For dependencies between modules you can use ${project.version} > In a near future (Maven 3.1 in theory) you won't have anymore to set the > version in the parent element if your module defines the relative path to its > parent or if it follows the convention to have it in its parent directory > To ensure to keep the same version everywhere you use the release plugin > which will update them for you. > The versions plugin could help you too. > > Cheers > > > Arnaud > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
