[
https://issues.jboss.org/browse/FORGE-1034?page=com.atlassian.jira.plugin...
]
George Gastaldi commented on FORGE-1034:
----------------------------------------
As replied in the e-mail:
{quote}
why is the forge-maven-plugin relevant for the eclipse plugins build ?
The
forge-maven-plugin retrieves the required addons in order to make Forge 2 usable in
Eclipse and copy them to an addon-repository folder that is created during build time.
This is to prevent binaries being pushed to the forge git repository. There is an older
version of the plugin already doing this but for some strange reason behind the classworld
land, Aether 1.13.1 (used to fetch the declared addons) does not work inside a maven
plugin targeted for 3.0.5.
And isn't requiring Mvn 3.1 in Forge 2 going to break other
plugins ?
I tested and the build works with Maven 3.1 AFTER Mickael upgraded the
tycho plugin version. So that is not an issue afaik.
afaics the mvn 3.1 release is getting many reports about
incompatibilities...
how does that affect our JBDS 7.0/7.1 where mvn 3.0 still needs to work too ?
That
should probably require some additional testing. I tested the JBT Forge build and the only
plugin that was preventing this to happen was the tycho I as beforementioned, which is now
fixed.
{quote}
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