Hi,
i've found a little issue based on an incompatibiliry of MVN 2.0.10/9
and MVN 2.1
I've defined some properties in my settings.xml:
homeoffice
devn-oracle-test
and based on that in my profiles.xml in the project there will be set
some properties:
devn-oracle-test
...
: Thursday, April 02, 2009 11:17 AM
To: users@maven.apache.org
Subject: Re: [ANN] Maven 2.1.0 Released
Rob and Brian,
Thanks for the response. However, how then does the maven-war-plugin
run. I do NOT specify an execution section for that plugin, and it runs
in the package phase.
So I am not sure
Rob,
Thanks! That clarifies things.
Pankaj
Sorry, I should have added that the element is only
required if the goal is not one of those in the lifecycle (corresponding to
the packaging type).
2009/4/2 Pankaj Tandon
>
> Rob and Brian,
> Thanks for the response. However, how then does the ma
Sorry, I should have added that the element is only
required if the goal is not one of those in the lifecycle (corresponding to
the packaging type).
2009/4/2 Pankaj Tandon
>
> Rob and Brian,
> Thanks for the response. However, how then does the maven-war-plugin run. I
> do NOT specify an execut
Rob and Brian,
Thanks for the response. However, how then does the maven-war-plugin run. I do
NOT specify an execution section for that plugin, and it runs in the package
phase.
So I am not sure why is it necessary to mention the execution element at all
(with or without a phase). Just the plug
The @phase will automatically cause a plugin to run at that phase, but
the plugin must still be mentioned in the pom.
-Original Message-
From: Pankaj Tandon [mailto:pankajtan...@gmail.com]
Sent: Thursday, April 02, 2009 10:40 AM
To: users@maven.apache.org
Subject: Re: [ANN] Maven 2.1.0
> you still have to declare an executions element for the very same phase in
the project that invkes this plugin.
That's right, except you don't have to specify the phase - the one declared
by the mojo will be assumed.
2009/4/2 Pankaj Tandon
>
> Hello Rob,
> I wanted to ask you about your comme
Hello Rob,
I wanted to ask you about your comment below where you state that even if you
have an annotation in a mojo for the execution phase, you still have to declare
an executions element for the very same phase in the project that invkes this
plugin.
That, kind of defeats the purpose of ha
Okay, my mistake - although it was indeed the 2.1.0 mvn which was in my
path, I had forgotten to change the value of my M2_HOME environment
variable.
Therefore, it was actually 2.0.10 which was being executed, which was why my
goal was being ignored.
And anyway, I had wrongly assumed that adding
As in a block in the pom.xml of the
jar-packaged project?
There isn't one, since the plugin's mojo has a '@phase prepare-package'.
2009/3/25 Brett Porter
>
>
> On 25/03/2009, at 10:07 PM, Rob Dickens wrote:
>
> Do jar-packaged projects now execute the new prepare-package phase?
>>
>> Have jus
On 25/03/2009, at 10:07 PM, Rob Dickens wrote:
Do jar-packaged projects now execute the new prepare-package phase?
Have just tried the new version out, hoping that my project with jar
packaging would execute the new phase, to which one of my plug-in
goals
declares itself as being bound, bu
Do jar-packaged projects now execute the new prepare-package phase?
Have just tried the new version out, hoping that my project with jar
packaging would execute the new phase, to which one of my plug-in goals
declares itself as being bound, but it appears not to.
Thanks,
2009/3/22 John Casey
>
On 22/03/2009, at 11:50 PM, Karl Heinz Marbaise wrote:
But on the other hand the web-site does not say a word about that ...
http://maven.apache.org/pom.html#Profiles to be more accurate they
are simply wrong, cause they are using:
Sure - please submit a JIRA ticket for the issue, and if y
My apologies, I just assumed the RCs were announced on the user list.
I see now they weren't so that's our fault. We'll announce the RCs on
the user list when we get near the cycle next time.
On 22-Mar-09, at 9:57 AM, Karl Heinz Marbaise wrote:
Hi Jason,
This is why we really encourage peo
Hi Jason,
This is why we really encourage people to participate in the RCs. We had
about 20 in total and we would have been able to do something for you if
you participated earlier.
If the RC's have been announced on the Users list it might work...but
from October last year (2008) till now (my
This is why we really encourage people to participate in the RCs. We
had about 20 in total and we would have been able to do something for
you if you participated earlier.
We still can, but we could have fixed it before it went into a
release. I think the quality of Maven has gone up expone
Hi Benjamin,
As per MNG-3645, the model is parsed in strict mode and is not a
valid child element of , it's a child of .
many thanks for the hint...fixed...
But now i'm running into a different problem, cause my profiles.xml
files does not work...The message says "Expected root element
'pro
Karl Heinz Marbaise wrote:
> I got messages about not recognised tag "timezone" in the POM..
> which is part of
>
>..
>
>
>
> +1
>
As per MNG-3645, the model is parsed in strict mode and is not a
valid child element of , it's a child of .
Benjamin
--
View th
Hi there,
i have tried to run MVN 2.1 on an working MVN 2.0.9 build...
and it failed...
I got messages about not recognised tag "timezone" in the POM..
which is part of
..
+1
...
But i haven't found any hint about this change ? May be i oversight things ?
The full p
19 matches
Mail list logo
