We have both Maven2 and 3 installed and working across our Jenkins infrastructure.
You should take a closer look at your master/slave configuration; you define the tools in the master, but also have to include the configuration in the slave; below is a part example of one of our Linux slaves. [cid:[email protected]] dD From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 22 July 2014 09:01 To: [email protected] Subject: Re: Can't execute Maven 2 on the slave where Maven 3 is installed There is also a configuration on jenkins under the slave for tool versions. On 21 Jul 2014 11:49 PM, "vicki_kozel via Jenkins Users" <[email protected]<mailto:[email protected]>> wrote: Hello, most of our projects are built with Maven 3. We have a request though to build one project with Maven 2. I installed Maven 2.2.1 on the slave boxes and configured a new maven entry in the Configure System space on the master. The build fails with the Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher exception. Any thoughts are greatly appreciated! Thank you Vicki -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
