|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-13754) Error when compiling... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)
- [JIRA] (JENKINS-13754) Error when comp... [email protected] (JIRA)

Would rather not leave Maven 2 workarounds in every plugin, especially as this dependency could easily be rendered stale by a core update.
Perhaps put an enforcer rule in the archetypal POM requiring Maven 3.0.4+, but with a comment linking to this issue explaining how you can make it work on Maven 2 if you need to.