Hi Mick,
I don't think there is any way to do what you are trying to do.
Having modules in a directory tree is just an optimisation; maven should be
able to build any module when it is just checked out on its own.
In other words, the <relativePath> tag is just an optimisation that works
*when* modules happen to be checked out together, but a pom *must* work when
the parent is only available via a lookup of the repository.
If a module is checked out on its own, and there is insufficient information to
find the parent without relying on the <relativePath> then that is an error.
So of course a version *must* be specified in the parent tag (otherwise there
is no way to know which version to pull from the repository). And that version
must *not* be defined in terms of data defined in the parent pom, otherwise an
obvious problem occurs: the parent pom would be needed to determine which
parent pom is needed.
Regards,
Simon
---- Mick Knutson <[EMAIL PROTECTED]> schrieb:
> I can comment out the modules <version> just fine then, but the parent:
>
> <parent>
> <groupId>org.delta.esp.dap.eep</groupId>
> <artifactId>services</artifactId>
> <version>1.0.2</version>
> <relativePath>../pom.xml</relativePath>
> </parent>
>
>
>
> Still is complaining if I do not have the version.
> I also tried ${org.delta.esp.dap.eep.version} as the version but it could
> not find it.
>
>
>
>
> On Jan 29, 2008 12:11 PM, Erez Nahir <[EMAIL PROTECTED]> wrote:
>
> > IMHO it should even be easier, just remove the <version> tag from the
> > child
> > poms.
> > It will inherit the version from the parent.
> >
> > Erez.
> >
> > On Jan 29, 2008 9:52 PM, Manos Batsis <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > I never actually managed to do that. IMHO that should be as easy as
> > >
> > > <version>${project.parent.version}</version>
> > >
> > > Oh well :-)
> > >
> > > Cheers,
> > >
> > > Manos
> > >
> > > Mick Knutson wrote:
> > > > I am actually trying to use a property:
> > > >
> > > > <org.delta.esp.dap.version>1.0.2</org.delta.esp.dap.version>
> > > >
> > > > Then use that property in my child pom's:
> > > >
> > > > ${org.delta.esp.dap.version}
> > > >
> > > > When I do an install and deploy it seems to work, but when I am doing
> > a
> > > > site-deploy, the parameter is not found and I get errors.
> > > >
> > > > Is there a better way?
> > > >
> > > >
> > > >
> > > > On Jan 29, 2008 10:23 AM, Arthur Rodrigues Stilben <
> > > > [EMAIL PROTECTED]> wrote:
> > > >
> > > >> Is there a way to use the version of a parent project in its
> > childrens
> > > >> projects?
> > > >>
> > > >> Arthur Rodrigues Stilben
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> 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]
> > >
> > >
> >
>
>
>
> --
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/BLiNCMagazine
> http://tahoe.baselogic.com
> ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
