AFAIR
property expansion is not performed in the parent tag... or maybe it's just
the version tag of the parent tag...
The logic is that it's not reproducible.
In my view this is the weakest link in Maven 2 as you then need to use the
release plugin to update all the child projects... makes changing the parent
a pain... which leads to people who don't understand about deploy being
essentially write-once trying to hack and modify the parent and "re-deploy"
it.
I'm not sure that I can see a better way though... unless 2.1 introduced the
concept of a tightly coupled child, i.e. if
<parent>
<relativePath>../pom.xml</relativePath>
</parent>
would just read the parent direct from the relative path. At deployment
time the parent details can be populated, but developers would not have to
worry while developing
-Stephen
On Jan 29, 2008 9:01 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> That did not work on the parent:
> <parent>
> <groupId>org.delta.esp.dap.eep</groupId>
> <artifactId>common</artifactId>
> *<version>${project.version}</version>*
> <relativePath>../pom.xml</relativePath>
> </parent>
>
>
> Still gives errors saying:
>
> *Reason: Unable to download the artifact from any repository
>
> org.delta.esp.dap.eep:common:pom:${project.version}
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)*<http://repo1.maven.org/maven2%29*>
>
>
>
>
> On Jan 29, 2008 12:28 PM, Rune Flobakk <[EMAIL PROTECTED]> wrote:
>
> > We're doing just that on the project I am working on; no version
> > specified in the child POMs, and it gets inherited from the parent POM.
> >
> > So since the child modules get the version implicitly, it should work
> > just referring to ${project.version}? (haven't tried it myself)
> >
> > -Rune
> >
> > Erez Nahir 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]
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > 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
> ---
>
