There shouldnt be a problem running maven3 in hudson - we've set it up as a freestyle job after all. The only real problem i see is that mvn3 is not yet installed in the slave we're using.
On Tue, Oct 19, 2010 at 19:00, Igor Drobiazko <[email protected]> wrote: > I'm using Maven 3.0 since couple of weeks. It works fine but there is a > problem with the tapestry-component-report plugin. Looks like we need to > port it. > > Another issue is that Hudson is not compatible with Maven 3.0. > > On Tue, Oct 19, 2010 at 5:55 PM, Howard Lewis Ship <[email protected]> wrote: > >> I've just upgraded my workstation to use Maven 3.0. I'm doing a full >> clean build (i.e., after deleting ~/.m2/repository). Looks like it >> works fine. >> >> My client using Artifactory to manage their Maven repositories has >> been having (unspecified) problems with the Tapestry JARs. I saw a >> cryptic note that the problem in Maven 2.2.x. Perhaps Maven 3.0 will >> fix that. >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
