|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
It's not the same thing. One is a special, magical job type that hooks into the Maven process to be able to not require configuration and do lots of automatic magic. Requires special support in Jenkins for every major(ish) Maven release, and is difficult to debug according to Stephen Connolly: http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html
The other is a nicer interface to the Maven command line call that just provides the Maven installation automatically if so configured.
Both are included out of the box probably more for historical reasons than anything else. Jenkins tries hard to not break backwards compatibility.