On Thu, 2003-12-11 at 18:34, Brett Porter wrote:
> ${pom.build.sourceDirectory}?
>
> I think we'll definitely need access to ${pom} in plugins and the project
> plugin (maven.xml or whatever the non-Jelly replacement is).
For certain, what I'm limiting is access to the ${pom} in the
project.properties
build.properties
> - Brett
>
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: Friday, 12 December 2003 1:19 AM
> > To: Maven Developers List
> > Subject: RE: Deprecation of POM interpolation in properties
> >
> >
> > On Wed, 2003-12-10 at 18:35, Brett Porter wrote:
> > > +1 if and only if there is away to do it via maven.xml (I
> > imagine the
> > > +below
> > > example becomes maven:pluginSetProperty plugin="maven-xdoc-plugin"
> > > property="maven.xdoc.version" value="${pom.currentVersion}" in a
> > > preGoal on xdoc:init).
> >
> > We could probably do that but I imagine with some thought
> > most of those things wouldn't be required.
> >
> > > - Brett
> > >
> > > > -----Original Message-----
> > > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > > Sent: Thursday, 11 December 2003 3:33 AM
> > > > To: Maven Developers List
> > > > Subject: Deprecation of POM interpolation in properties
> > > >
> > > >
> > > > Howdy,
> > > >
> > > > I'm moving along with the maven-project component and I have
> > > > arbitrary levels of inheritance working for properties
> > and the model.
> > > >
> > > > Now I'm starting to look at the property interpolation
> > > > mechanism and I would like to propose for 1.1 that values in
> > > > properties files be interpolated in the model values but
> > > > ${pom.foo} values not be interpolated in properties values.
> > > >
> > > > The first reason is that it makes the process a lot more
> > > > clear and second I'm not sure if having model values
> > > > interpolated in properties values is really of any use. I
> > > > think when we have cases like:
> > > >
> > > > maven.xdoc.version = ${pom.currentVersion}
> > > >
> > > > We could really just use the ${pom.currentVersion} directly
> > > > in the relevant plugin instead of putting it in a property
> > > > and then sucking it back in.
> > > >
> > > > At any rate, to make the project processing in 1.1 highly
> > > > deterministic I would like to remove ${pom.foo} value
> > > > interpolation in properties files.
> > > >
> > > > --
> > > > jvz.
> > > >
> > > > Jason van Zyl
> > > > [EMAIL PROTECTED]
> > > > http://tambora.zenplex.org
> > > >
> > > > In short, man creates for himself a new religion of a
> > > > rational and technical order to justify his work and to be
> > > > justified in it.
> > > >
> > > > -- Jacques Ellul, The Technological Society
> > > >
> > > >
> > > >
> > --------------------------------------------------------------------
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > --
> > jvz.
> >
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://tambora.zenplex.org
> >
> > In short, man creates for himself a new religion of a
> > rational and technical order to justify his work and to be
> > justified in it.
> >
> > -- Jacques Ellul, The Technological Society
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
