s 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 interpolati
x27;t know when.
-Original Message-
From: [EMAIL PROTECTED]
To: Maven Developers List
Sent: 12/11/2003 6:20 PM
Subject: Re: Deprecation of POM interpolation in properties
It has been very useful in the past
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
It has been very useful in the past
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jason van Zyl <[EMAIL PROTECTED]> wrote on 12/12/2003 01:21:11 AM:
> Howdy,
>
> I am going to work on some docs today and I will get the site up for the
> components
r 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
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 p
On Wed, 2003-12-10 at 12:58, Steve Garcia wrote:
> > On Wed, 2003-12-10 at 11:33, Jason van Zyl wrote:
> > > 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 starti
On Wed, 2003-12-10 at 18:32, matt wrote:
> If I've understood what you're suggesting, we currently depend on this
> feature.
Yes, but I'm asking you to think about why you are and if it would be
possible to achieve what you are after without it.
> As an example, in order to get war:webapp to bui
+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).
- Brett
> -Original Message-
> From: Jason van Zyl [mailto
If I've understood what you're suggesting, we currently depend on this
feature.
As an example, in order to get war:webapp to build to a directory named
".war" (which is necessary for in-place deployment), we must override
maven.war.webapp.dir, and in order to produce versioned war archives
(wh
> On Wed, 2003-12-10 at 11:33, Jason van Zyl wrote:
> > 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
> >
On Wed, 2003-12-10 at 11:33, Jason van Zyl wrote:
> 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 fo
11 matches
Mail list logo