Maven 3.5 in use even for Maven 3.3.9 targets?

["John D. Ament" <jo...@apache.org>]

I just downgraded one of my builds to use Maven 3.3.9, not realizing we had
the 3.5 fix in place.  When I did, I noticed this problem:

Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 42643
maven35-agent.jar already up to date
maven35-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[DeltaSpike for CDI 2.0] $ /home/jenkins/tools/java/jdk1.8.0_131/bin/java
-Xmx2g -Xms256m -cp
/home/jenkins/jenkins-slave/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging
jenkins.maven3.agent.Maven35Main
/home/jenkins/tools/maven/apache-maven-3.3.9
/home/jenkins/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven35-interceptor.jar
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 42643
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven:  -B -f /home/jenkins/jenkins-slave/workspace/DeltaSpike
for CDI 2.0/pom.xml
-Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 clean
install -Prat
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at jenkins.maven3.agent.Maven35Main.launch(Maven35Main.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:139)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/shared/utils/logging/MessageUtils
at
org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.populateRequest(DefaultMavenExecutionRequestBuilder.java:767)
at
org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:153)
at
org.jvnet.hudson.maven3.launcher.Maven35Launcher.getMavenExecutionRequest(Maven35Launcher.java:151)
at
org.jvnet.hudson.maven3.launcher.Maven35Launcher.main(Maven35Launcher.java:128)
... 21 more

It seems like we're pulling in Maven 3.5 libraries even for 3.3.x maven
installations.  Is that on purpose?  (Build can be found at
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20for%20CDI%202.0/151/console
 )

John