Hey Jarcec, Have you tried reversing the path export for example:
export MAVEN_HOME=/home/jenkins/tools/maven/latest export PATH=$JAVA_HOME/bin:$MAVEN_HOME/bin:$PATH To ensure your "mvn" command is picked up first even if it's on the existing PATH. David -----Original Message----- From: Jarek Jarcec Cecho [mailto:jar...@gmail.com] On Behalf Of Jarek Jarcec Cecho Sent: Friday, 16 October 2015 6:21 AM To: builds@apache.org Cc: d...@sqoop.apache.org Subject: Re: How can we choose the right maven version for our build? Any ideas how to pick up the proper version of maven? Jarcec > On Aug 24, 2015, at 1:20 PM, Jarek Jarcec Cecho <jar...@apache.org> wrote: > > I have a job that is quite regularly failing with: > > Error resolving version for 'org.codehaus.mojo:findbugs-maven-plugin': Plugin > requires Maven version 3.0.1 > > Looking into the job’s configuration, I don’t see any way to specify maven > version (similarly as we do for let say java). It seems that we were trying > to deal with this in the past as the we’re having following “Detection” in > the command we’re running: > > export MAVEN_HOME=/home/jenkins/tools/maven/latest > export PATH=$PATH:$JAVA_HOME/bin:$MAVEN_HOME/bin > > But that sees quite flaky, so I’m wondering what is the right way to get the > right maven version for the job? :) > > Jarcec > > Links: > 1: > https://builds.apache.org/job/PreCommit-SQOOP-Build/1622/artifact/patch-process/test_unit.txt
