This has been discussed for the release plugin. The thing is, someone has to
implement it. Maybe this "someone" is you?
Btw, sorry for the previous empty mail. I blame my phone...
/Anders (mobile)
Den 2 jun 2011 00.23 skrev "Russ Tremain" :
> At 9:26 PM +0200 5/29/11, Arnaud Héritier wrote:
>>For
/Anders (mobile)
Den 2 jun 2011 00.23 skrev "Russ Tremain" :
> At 9:26 PM +0200 5/29/11, Arnaud Héritier wrote:
>>For now it is just impossible to use properties in GAV for various
technical
>>and also philosophical reasons.
>
>
> I still don't see why the maven deployment plugin cannot be responsi
At 9:26 PM +0200 5/29/11, Arnaud Héritier wrote:
>For now it is just impossible to use properties in GAV for various technical
>and also philosophical reasons.
I still don't see why the maven deployment plugin cannot be responsible for
hardening artifact properties inside deployed poms.
The help
For now it is just impossible to use properties in GAV for various technical
and also philosophical reasons.
You may not be agree with the philosophy behind this choice but it is sure
that for now it is more secure in Maven to avoid this usage as it creates
many issues.
About the philosophy even i
Why dont you use the buildnumber plugin? That might be able to do it for
you..
http://mojo.codehaus.org/buildnumber-maven-plugin/
> For what it's worth, I agree with you both (version strings should be
> controlled via the -ahem- version control system), but I am willing to
> allow Maven (more to
For what it's worth, I agree with you both (version strings should be
controlled via the -ahem- version control system), but I am willing to
allow Maven (more to the point, the maven-release-plugin) to take care
of the version strings for me.
However, if you don't want to, you can still do it your
+1.
this is the major reason I won't be upgrading to maven 3.
I do think that versions should be fixed at maven deploy time - i.e., when
artifacts are deployed to the repository.
-Russ
At 5:21 AM -0700 3/26/11, bryan.dollery wrote:
>Hi,
>
>I am also getting grief from maven for using variables
On 28/03/2011 4:30 AM, bryan.dollery wrote:
Hi Ron,
Maven isn't meant to be enforcing convention. It's meant to work without
configuration /if/ convention fits in your particular domain. Where
convention doesn't fit it's meant to be configurable.
To a certain extent that is true but as you can s
Hi Ron,
Maven isn't meant to be enforcing convention. It's meant to work without
configuration /if/ convention fits in your particular domain. Where
convention doesn't fit it's meant to be configurable.
As for best practice... Using maven for version management is /not/ best
practice. It's a con
On 26/03/2011 8:21 AM, bryan.dollery wrote:
Hi,
I am also getting grief from maven for using variables in my version fields.
For me, this is unavoidable. Let me explain...
In my parent pom I have:
${productVersion}
And in my properties I have:
0-SNAPSHOT
13.0.${productRevis
Hi,
I am also getting grief from maven for using variables in my version fields.
For me, this is unavoidable. Let me explain...
In my parent pom I have:
${productVersion}
And in my properties I have:
0-SNAPSHOT
13.0.${productRevision}
On a developer's machine, this produces a
2010/3/12 Trojan, Krzysztof
> Hi,
>
> > Well, if I read correctly what you said, you're putting the dependencies
> between project with external properties that defines versions. I guess you
> know one of the main objectives of maven is letting users be able to have an
> always reproducible build
n version, or actually any other part
of the pom, is that one step too far.
Regards,
Krzysztof Trojan
From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS
Sent: 12 March 2010 14:22
To: Maven Users List
Cc: Trojan, Krzysztof
Subject: Re: Maven 3.0 Artefact/Dependency ve
Answering putting Krzysztof in copy. But please, subscribe to the users
maven list, because not sure everybody will think about clicking on "reply
all".
Well, if I read correctly what you said, you're putting the dependencies
between project with external properties that defines versions. I guess
The user list is here users@maven.apache.org and you can subscribe to discuss
your issues using users-subscr...@maven.apache.org.
On Mar 10, 2010, at 5:45 AM, Trojan, Krzysztof wrote:
> Dear Sir,
>
> First of all I would like to apologize for writing to you directly. I have
> inadequate infor
15 matches
Mail list logo
