>>
>> Romain.
>>
>>
>> -----Original Message-
>> From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
>> Sent: 18 February 2009 01:31
>> To: Maven Users List
>> Subject: RE: Removing: jar from forked lifecycle, to prevent recursive
>>
> >
I don't know if you are still looking for an answer to how to fix this
problem but what I found to fix the problem for me was to change the
maven-source-plugin goal from jar to jar-no-fork. I also had to add
2.1 as well. You may also need to change test-jar to
test-jar-no-fork.
The informa
st'
> Subject: RE: Removing: jar from forked lifecycle, to prevent
> recursive invocation
>
> I am wondering if Brian, or any other Maven expert our there,
> could explain how this warning could be avoided entirely. I
> have looked into this at length when adding, for ex
. Fox [mailto:bri...@reply.infinity.nu]
> Sent: Tuesday, February 17, 2009 7:31 PM
> To: Maven Users List
> Subject: RE: Removing: jar from forked lifecycle, to prevent
> recursive invocation
>
> This means the plugin that caused the fork to occur is
> removed from that fork
; To: Maven Users List
> Subject: RE: Removing: jar from forked lifecycle, to prevent recursive
> invocation
>
> This means the plugin that caused the fork to occur is removed from that
> forked lifecycle so it doesn't fork again.
>
> -Original Message-
> From: R
Is it a dangerous for my build ?
If yes, how can I find where the problem comes from ?
Thanks,
Romain.
-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: 18 February 2009 01:31
To: Maven Users List
Subject: RE: Removing: jar from forked lifecycle, to prevent
This means the plugin that caused the fork to occur is removed from that
forked lifecycle so it doesn't fork again.
-Original Message-
From: Romain Gilles [mailto:romain.gil...@thomsonreuters.com]
Sent: Tuesday, February 17, 2009 5:08 AM
To: Maven Users List
Subject: Removing: jar from fo
