On 16/10/2012, at 8:35 AM, Barrie Treloar wrote:
> On Fri, Apr 6, 2012 at 12:31 AM, Wayne Fay wrote:
>> On Thu, Apr 5, 2012 at 5:36 AM, wrote:
>>>
>>> I will be out of the office starting 04/05/2012 and will not return until
>>> 04/10/2012.
>>
>> Makes me wonder what Julia Antonova/Tumlare
On Fri, Apr 6, 2012 at 12:31 AM, Wayne Fay wrote:
> On Thu, Apr 5, 2012 at 5:36 AM, wrote:
>>
>> I will be out of the office starting 04/05/2012 and will not return until
>> 04/10/2012.
>
> Makes me wonder what Julia Antonova/Tumlare is up to lately... and
> when her next vacation is!
I think
I will be out of the office starting 10/15/2012 and will not return until
10/18/2012.
If your request is urgent, please contact Björn Domschke.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands
Hi Olivier
Do you know if there has been any progress on this?
I found this issue that tracks the regression in Jenkins JIRA:
https://issues.jenkins-ci.org/browse/JENKINS-15367
We really need to get this fixed before we put Maven 3 + ITs in Git and
running the builds on Jenkins. As an example I h
Just did a little digging ... so assuming I have only two projects ... one
master and one module.
If I define two properties in my master pom: "my.cool.master.version" and
"my.cool.alternate.master.version" and set both to the same value of
"1.2-SNAPSHOT".
In szenario 1: I ´hard code the versi
On 15 October 2012 16:56, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:
> Hmm ... but if the effective defaults are as you claim, why does this even
> work correctly, if the versions of every artifact is completely different?
>
> Unfortunatley this unintentional working feature cur
Hmm ... but if the effective defaults are as you claim, why does this even work
correctly, if the versions of every artifact is completely different?
Unfortunatley this unintentional working feature currently seems to be the only
"feature" allowing me to define a really nicely working build. The
The Maven team is pleased to announce the release of the Maven Site Plugin 3,
version 3.2
The Maven Site Plugin is a plugin that generates a site for the current project.
http://maven.apache.org/plugins/maven-site-plugin
You should specify the version in your project's plugin configuration:
Those are edge cases where things unintentionally work, probably falling
out of the way the model is built in memory.
e.g.
/project/version has an effective default value of ${project.parent.version}
/project/groupId has an effective default value of ${project.parent.groupId}
I say "effective" a
I know that property substitution in those places seems to be unavailable.
But there seems to be one case where it's seems to be explicitly allowed:
If the parent artifacts version is defined by the same variable used to
reference the parent pom, maven doesn't complain about anything (So I guess
On 15 October 2012 15:13, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:
> Hi,
>
> I just opened an issue regarding the install plugin (I think that's the
> module responsible).
> http://jira.codehaus.org/browse/MNG-5358
>
> The general problem is that I am using variables for defin
Hi,
I just opened an issue regarding the install plugin (I think that's the module
responsible).
http://jira.codehaus.org/browse/MNG-5358
The general problem is that I am using variables for defining the versions of
artifacts, dependencies and parent projects. The install plugin installs the
p
Guys, you rock!
I also like to add my thanks to Stephen as he started the
plexus-utils-commons-bridge over in our sandbox. Without this work we would not
have been able to do this so fast. Also a thanks to all guys who helped
importing the stuff they wrote into this module.
LieGrue,
strub
13 matches
Mail list logo