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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to