[jbosstools-issues] [JBoss JIRA] (JBIDE-12292) Use m2e-wtp dev builds in composite sites and aggregate builds (rather than in Juno target platform)
[
https://issues.jboss.org/browse/JBIDE-12292?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12292:
----------------------------------------
Nick, I see target-platforms use static versions for dependencies, including m2e-wtp. If
we use the procedure you describe, then we'll also need to modify version for m2e-wtp
in target-platforms every time a new build and new qualifier is produced for m2e-wtp. Am I
right?
Shouldn't we in such case put 0.0.0 as version for m2e-wtp in target-platforms?
Use m2e-wtp dev builds in composite sites and aggregate builds
(rather than in Juno target platform)
----------------------------------------------------------------------------------------------------
Key: JBIDE-12292
URL: https://issues.jboss.org/browse/JBIDE-12292
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.4.0.M1
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 3.4.0.M1
Our maven features should now depend on m2e-wtp @ eclipse.
However, there's no stable build available from Eclipse yet. We should use the
development update site to point to the latest m2e-wtp 0.16.0 build :
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w...
[~mickael_istria] suggests to add that repo in the pom.xml's repositories
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira