June 23, 2008 7:47 PM
To: Maven Developers List
Subject: RE: [PROPOSAL] Refactoring POM Interpolation for Maven 2.0.10
You know someone is going to also desire not just the timestamp, but
only
the time, or just the date. If you're doing the work now, might as
well
throw in the other 2.
ian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2008 7:47 PM
To: Maven Developers List
Subject: RE: [PROPOSAL] Refactoring POM Interpolation for Maven 2.0.10
>You know someone is going to also desire not just the timestamp, but
only
>the time, or just the date. If you're doing t
>You know someone is going to also desire not just the timestamp, but
only
>the time, or just the date. If you're doing the work now, might as well
>throw in the other 2.
Then they can use the buildnumber plugin for this. I don't subscribe to
the slippery-slope theory that just because we make som
rent formats in the same POM). Possibly
> getting a bit "out there", but what if we could paramaterise interpolation
> for certain formats instead? eg. ${maven.build.timestamp|format='MMdd'}
>
> Cheers,
> Brett
>
>
> On 17/06/2008, at 3:35 AM, John Cas
ssibly getting a bit "out there", but what if we
could paramaterise interpolation for certain formats instead? eg. $
{maven.build.timestamp|format='MMdd'}
Cheers,
Brett
On 17/06/2008, at 3:35 AM, John Casey wrote:
Hi everyone,
I wanted to start another discussion
Hi everyone,
I wanted to start another discussion having to do with POM interpolation
in the upcoming Maven 2.0.10 release. If you recall, I previously sent
out a proposal for retaining dynamic expressions in the build section of
the POM, to allow updates to that section that take place via
Sure. I'll take a look when I get a chance, but I just wanted to check whether
this might block a 1.0 release.
Cheers,
Brett
Quoting Gilles Dodinet <[EMAIL PROTECTED]>:
> Brett Porter wrote:
>
> > Gilles,
> >
> > Is this an issue you get when you run Maven or only when you utilise
> > the code
Brett Porter wrote:
Gilles,
Is this an issue you get when you run Maven or only when you utilise
the code in Mevenide?
Brett,
this problem appears only within mevenide, so there is definitively
something i must be be doing wrong but i cannot see what step im missing.
thanks,
-- gd
-
Gilles,
Is this an issue you get when you run Maven or only when you utilise the
code in Mevenide?
Thanks,
Brett
Gilles Dodinet wrote:
hi-
while working on mevenide, i experiment a strange behaviour : i
unmarshall the pom with xpp3, then set the context through a call to
project.setContext(..),
Gilles Dodinet wrote:
however if i use jar override
(maven.jar.myproject=lib/myproject-${pom.currentVersion}.jar), a call
to myArtifact.getPath() returns this :
[prepend is correctly set]/lib/myproject-.jar (i.e. pom.currentVersion
is not resolved)
here is a bit more details. if i declare :
to
hi-
while working on mevenide, i experiment a strange behaviour : i
unmarshall the pom with xpp3, then set the context through a call to
project.setContext(..), then build the artifact list with
ArtifactListBuilder :
project.setContext(MavenUtils.createContext(project.getFile().getParentFile())
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
Howdy,
I am going to work on some docs today and I will get the site up for the
components so there will be a description for the behaviour of property
interpolation but please give it some thought if you have some time as I
don't want to get to 1.1 and someone go "but blah blah blah blah, I NEED
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 200
; > 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.
> >
> > Another point that I wanted to raise was that properties may
> > ultima
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.
>
essage-
> 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
raise was that properties may ultimately
come from other sources such as database, or ldap and how much sense
does it make for those sources to have access to the POM. I honestly
don't think a whole lot. I think properties should just be flat
raise was that properties may
> ultimately come from other sources such as database, or ldap
> and how much sense does it make for those sources to have
> access to the POM. I honestly don't think a whole lot. I
> think properties should just be flat name/value
s database, or ldap and how much sense
does it make for those sources to have access to the POM. I honestly
don't think a whole lot. I think properties should just be flat
name/value pairs with no ${pom} interpolation.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In s
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 mod
24 matches
Mail list logo
