But you can't do this?:
<version>${project.parent.version}</version>
Sure would be nice to be able to keep my versions in sync more easily
if I don't want to bother independently versioning
modules/sub-projects.
-Stephen
On 10/1/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> <version>${project.version}</version>
>
> will do the trick. You can still self reference the model.
>
> - Brett
>
> Alan D. Cabrera wrote:
>
> > I have a suggested enhancement. Maybe this is already available.
> > Maybe it's a bad idea. Here it is.
> >
> > Frequently, I will have multiple projects that are interdependent.
> > Their versions will move in tandem as I change the root POM's
> > version. IIUC, when I change the root POM's version, I must also
> > change the versions of the projects in the <dependencyManagement>
> > list. What would be neat is to have an element, say <useRootVersion/>
> > which I could add to the <version> element. This will inform
> > dependency management that the version of this dependency is to move
> > in tandem with the root <model><version/> element.
> >
> > Thoughts?
> >
> >
> > Regards,
> > Alan
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
