I switched my stuff to invoker. Wasn't too hard. Very similar.
on Monday, April 13, 2009 6:30:18 AM Jason Dillon said
>I'll fix this shortly, but you are free to move to the invoker if you like...
>haven't used the invoker for a while, not sure what the major differences are.
>
>--jason
On
I'll fix this shortly, but you are free to move to the invoker if you
like... haven't used the invoker for a while, not sure what the major
differences are.
--jason
On Apr 10, 2009, at 3:15 PM, Olivier Lamy wrote:
Hi folks,
I wanted to work on buildnumber-maven-plugin and it looks shitty
Hi,
Done for ones which are in the ci-aggregator pom.
And job in the grid configured to use mvn 2.1.0
--
Olivier
2009/4/10 Dan Tran :
> On Fri, Apr 10, 2009 at 1:33 AM, Benjamin Bentmann
> wrote:
>> Olivier Lamy wrote:
>>
>>> I wanted to work on buildnumber-maven-plugin and it looks shitty
>>> p
On Fri, Apr 10, 2009 at 1:33 AM, Benjamin Bentmann
wrote:
> Olivier Lamy wrote:
>
>> I wanted to work on buildnumber-maven-plugin and it looks shitty
>> plugin break with mvn 2.1.0.
>
> This was anticipated some time ago: MSHITTY-10
>
> Moving the CI build to Maven 2.1.0 would in particular be use
Olivier Lamy wrote:
I wanted to work on buildnumber-maven-plugin and it looks shitty
plugin break with mvn 2.1.0.
This was anticipated some time ago: MSHITTY-10
Moving the CI build to Maven 2.1.0 would in particular be useful to get
rid of MNG-3284 which otherwise can screw up reactor builds
Hi folks,
I wanted to work on buildnumber-maven-plugin and it looks shitty
plugin break with mvn 2.1.0.
Have a look here
https://grid.sonatype.org/ci/view/Mojo/job/Mojo-Trunk/187/jdk=1.5,label=ubuntu/console.
So what to do ? (moving to invoker plugin ? )
Thanks,
--
Olivier
--
