This caught my eye. I have no idea what it means though or if it could
be responsible for the problem.
The following artifacts were filtered out for plugin:
org.apache.commons:commons-build-plugin:1.0 because they're already in the core
of Maven:
Niall Pemberton wrote:
On Sat, Jun 28, 2008
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> What does -X tell you?
Not alot that makes any sense to me, but thanks for the suggestion - I
ran it with that option for both maven 2.0.8 and 2.0.9 and the output
for both is here:
http://people.apache.org/~niallp/commons-
What does -X tell you?
Niall Pemberton wrote:
Anyone got any ideas on this - should I open a JIRA ticket (if so
against what?) or should I have asked this on the user list? I posted
here coz it looks like a maven bug to me.
Niall
On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton
<[EMAIL PROTECT
Anyone got any ideas on this - should I open a JIRA ticket (if so
against what?) or should I have asked this on the user list? I posted
here coz it looks like a maven bug to me.
Niall
On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton
<[EMAIL PROTECTED]> wrote:
> I recently upgraded from maven 2.0.
Hi,
FYI I created MNG-3634 and you could see the result here:
http://people.apache.org/~vsiveton/MNG-3634/maven-2.0.x/site/maven.html
Comments are welcome!
Cheers,
Vincent
2008/6/23, Vincent Siveton <[EMAIL PROTECTED]>:
> Hi,
>
> I propose to improve [1] to add a code style for our pom files.
