[
https://issues.jboss.org/browse/FORGE-1034?page=com.atlassian.jira.plugin...
]
Mickael Istria edited comment on FORGE-1034 at 7/31/13 8:42 AM:
----------------------------------------------------------------
I've tried to update JBT Forge module CI job to use Maven 3.1, but Maven 3.1 is not
yet available on Jenkins. When available, it will just be a matter of updating CI job, and
you'll be free to update the version of forge-maven-plugin.
But currently, there is no Maven 3.1 available.
I let [~maxandersen] debate with you about the goodness/badness of switching so early to
Maven 3.1.
was (Author: mickael_istria):
I've updated JBT Forge module CI job to use Maven 3.1, so you'll be free to
use the newer version of forge-maven-plugin.
This should solve all build issues and let you go ahead.
I let [~maxandersen] debate with you about the goodness/badness of switching so early to
Maven 3.1.
Upgrade forge-maven-plugin to use furnace-manager
-------------------------------------------------
Key: FORGE-1034
URL:
https://issues.jboss.org/browse/FORGE-1034
Project: Forge
Issue Type: Component Upgrade
Components: Maven Plugin
Affects Versions: 2.0.0.Alpha6
Reporter: George Gastaldi
Assignee: George Gastaldi
--
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