The issues with the ci-aggregator have been solved.
Main reason of the problems was the maven-invoker-plugin-1.3
By updating the version to 1.5 the issues disappeared.
I'll check this RC with some other projects as well.
-Robert
@Anders, it looks like you're right, see components.xml[1]
[1] http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml?view=markup#l116
On Tue, 27 Dec 2011 11:09:18 +0100, Anders Hammar <and...@hammar.net> wrote:
> I just noticed that v2.0.1 is still the default version of the
> maven-site-plugin. I was under the impression that once v3.0 of
> m-site-p was released, this would change so that we have a workable
> site configuration out-of-the-box.
> I can't find a jira ticket for this so I must have misunderstood
> things. But it's unfortunate that we still have unworkable site part
> with Maven defaults. I'll file a ticket for this to be fixed in a
> future version.
>
> /Anders
>
> On Sat, Dec 24, 2011 at 22:25, Robert Scholte <rfscho...@codehaus.org>
> wrote:
>>
>> Hmm, I need a new webclient. Now with the right linebreaks...
>>
>>
>>
>> As some might know, we're having trouble to run the mojo's
>> ci-aggregator on our Bamboo[1]
>> It is always complaining about an empty maven-plugin-api.pom or an
>> empty classworlds.pom
>> I checked out the complete mojo-project to run it on my own system and
>> I faced the same problem.
>> If I check the folder I see that 2 files have changed at the same
>> moment: the mentioned pom and the _maven.repositories
>>
>> Here's a result of the
>> org/apache/maven/maven-plugin-api/2.0/_maven.repositories
>> #NOTE: This is an internal implementation file, its format can be
>> changed without prior notice.
>> #Sat Dec 24 17:44:57 CET 2011
>> maven-plugin-api-2.0.pom>central=
>> maven-plugin-api-2.0.jar>=
>> maven-plugin-api-2.0.pom>=
>> maven-plugin-api-2.0.pom>nexus=
>> maven-plugin-api-2.0.jar>central=
>>
>> And yes, the pom is zero bytes.
>>
>> I think it has to do with the difference between the 'normal' build and
>> the invoker-maven-plugin.
>> I'm not sure if this is the same issue as MNG-5181, but it looks
>> related to me.
>>
>> I'll try it with other Maven versions too.
>> To be continued.
>>
>> -Robert
>>
>> [1] http://bamboo.ci.codehaus.org/browse/MOJO-CIAGGREGATOR
>> [2] https://jira.codehaus.org/browse/MNG-5181
>>
>>
>>
>>
>> From: mfriedenha...@gmail.com
>>> > Date: Sat, 24 Dec 2011 21:23:23 +0100
>>> > Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC4 staged
>>> > To: dev@maven.apache.org
>>> >
>>> > FYI - runs fine on my Jenkins instance and my Mac.
>>> >
>>> > Regards Mirko
>>> >
>>> > On Fri, Dec 23, 2011 at 19:58, Jesse Glick <jesse.gl...@oracle.com>
>>> wrote:
>>> > > FYI - again integrated into NetBeans development builds to spur
>>> testing.
>>> > >
>>> > >
>>> > >
>>> > >
>>> ---------------------------------------------------------------------
>>> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> > > For additional commands, e-mail: dev-h...@maven.apache.org
>>> > >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> > For additional commands, e-mail: dev-h...@maven.apache.org
>>> >
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
On Tue, 27 Dec 2011 11:09:18 +0100, Anders Hammar <and...@hammar.net> wrote:
> I just noticed that v2.0.1 is still the default version of the
> maven-site-plugin. I was under the impression that once v3.0 of
> m-site-p was released, this would change so that we have a workable
> site configuration out-of-the-box.
> I can't find a jira ticket for this so I must have misunderstood
> things. But it's unfortunate that we still have unworkable site part
> with Maven defaults. I'll file a ticket for this to be fixed in a
> future version.
>
> /Anders
>
> On Sat, Dec 24, 2011 at 22:25, Robert Scholte <rfscho...@codehaus.org>
> wrote:
>>
>> Hmm, I need a new webclient. Now with the right linebreaks...
>>
>>
>>
>> As some might know, we're having trouble to run the mojo's
>> ci-aggregator on our Bamboo[1]
>> It is always complaining about an empty maven-plugin-api.pom or an
>> empty classworlds.pom
>> I checked out the complete mojo-project to run it on my own system and
>> I faced the same problem.
>> If I check the folder I see that 2 files have changed at the same
>> moment: the mentioned pom and the _maven.repositories
>>
>> Here's a result of the
>> org/apache/maven/maven-plugin-api/2.0/_maven.repositories
>> #NOTE: This is an internal implementation file, its format can be
>> changed without prior notice.
>> #Sat Dec 24 17:44:57 CET 2011
>> maven-plugin-api-2.0.pom>central=
>> maven-plugin-api-2.0.jar>=
>> maven-plugin-api-2.0.pom>=
>> maven-plugin-api-2.0.pom>nexus=
>> maven-plugin-api-2.0.jar>central=
>>
>> And yes, the pom is zero bytes.
>>
>> I think it has to do with the difference between the 'normal' build and
>> the invoker-maven-plugin.
>> I'm not sure if this is the same issue as MNG-5181, but it looks
>> related to me.
>>
>> I'll try it with other Maven versions too.
>> To be continued.
>>
>> -Robert
>>
>> [1] http://bamboo.ci.codehaus.org/browse/MOJO-CIAGGREGATOR
>> [2] https://jira.codehaus.org/browse/MNG-5181
>>
>>
>>
>>
>> From: mfriedenha...@gmail.com
>>> > Date: Sat, 24 Dec 2011 21:23:23 +0100
>>> > Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC4 staged
>>> > To: dev@maven.apache.org
>>> >
>>> > FYI - runs fine on my Jenkins instance and my Mac.
>>> >
>>> > Regards Mirko
>>> >
>>> > On Fri, Dec 23, 2011 at 19:58, Jesse Glick <jesse.gl...@oracle.com>
>>> wrote:
>>> > > FYI - again integrated into NetBeans development builds to spur
>>> testing.
>>> > >
>>> > >
>>> > >
>>> > >
>>> ---------------------------------------------------------------------
>>> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> > > For additional commands, e-mail: dev-h...@maven.apache.org
>>> > >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> > For additional commands, e-mail: dev-h...@maven.apache.org
>>> >
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
