Ok, the hosted Maven3.0.2 works fine with the current version of our pom (which now (kinda) requires m3).
Most important: the nightly builds works, as they worked before. So, that part would be fixed - for now I am keeping this "improvement", at least temporary. (I will keep 2006 open for a bit, even it looks like we solved it) -M On Thu, Jan 27, 2011 at 9:12 AM, Matthias Wessendorf <mat...@apache.org> wrote: > As expected, the build failed locally and on hudson (see > TRINIDAD-2006) due to the site plugin. > > However it is possible to use our Hudson machine with Maven 3.0.2 - > currently I am doing that, > with the patch from TRINIDAD-2006. > > -M > > On Thu, Jan 27, 2011 at 7:16 AM, Matthias Wessendorf <mat...@apache.org> > wrote: >> Hi, >> >> what are folks thinking about using Maven3. I did some tests for >> Trinidad and Maven 3 yesterday ([1]). >> Things like the regular build and site generation is working fine. I >> am not (yet) 100% how our (Apache) Hudson >> build machine like Maven3 (I used 3.0.2). >> >> However we can simply test that. >> >> I wonder if folks would mind, if the Trinidad build (as a starter...) >> would be "requiring" Maven3.x, in the near future? >> >> Greetings, >> Matthias >> >> [1] https://issues.apache.org/jira/browse/TRINIDAD-2006 >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf