-
Bug
-
Resolution: Fixed
-
Major
-
None
When used with a maven installation set to automatically install maven, build fails with "ERROR: Maven 'Maven 3.0.4' doesn't have its home set"
hudson.maven.AbstractMavenProcessFactory.getMavenInstallation and hudson.tasks.Maven performs the node translation (which is responsible for running installers etc. as well).
org.jfrog.hudson.maven3.Maven3Builder don't.
according to javadoc, jfrog Maven3Builder is designed as a "Maven3 builder for free style projects. Hudson 1.392 added native support for maven 3 but this one is useful for free style."
jenkins standard Maven freestyle build step fully supports maven3, so I really don't understand why this build step exists. Should at least re-use maven-plugin's Maven3ProcessFactory to avoid this bug, or probably be deprecated with migration code to convert to hudson.task.Maven