[
https://issues.jboss.org/browse/JBIDE-12292?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12292 at 7/6/12 12:23 PM:
-------------------------------------------------------------
Proposed solution - treat m2e-wtp like another JBT component:
a) add m2e-wtp nightly build URL [0] to
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun...
so JBT aggregate site can find it like other components / upstream
b) add m2e-wtp nightly build URL [0] to associate.properties [1] so it can me
automatically found when installing from
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
c) add m2e-wtp nightly build URL [0] as new repository to JBDS product pom [2]
d) add m2e-wtp nightly build URL [0] to composite staging site for JBDS 6.0 [3]
[0]
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w...
[1]
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
(and other aggregates like coretests, soa, etc.)
[2]
https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml
[3]
https://devstudio.jboss.com/updates/6.0/staging/ (forthcoming, does not exist yet)
We should also unlink m2e-apt site from parent pom and other places and use this similar
approach instead (JBIDE-12294).
was (Author: nickboldt):
Proposed solution - treat m2e-wtp like another JBT component:
a) add m2e-wtp nightly build URL [0] to
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun...
so JBT aggregate site can find it like other components / upstream
b) add m2e-wtp nightly build URL [0] to associate.properties [1] so it can me
automatically found when installing from
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
c) add m2e-wtp nightly build URL [0] as new repository to JBDS product pom [2]
d) add m2e-wtp nightly build URL [0] to composite staging site for JBDS 6.0 [3]
[0]
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... I
presume?
[1]
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
(and other aggregates like coretests, soa, etc.)
[2]
https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml
[3]
https://devstudio.jboss.com/updates/6.0/staging/ (forthcoming, does not exist yet)
We should also unlink m2e-apt site from parent pom and other places and use this similar
approach instead (JBIDE-12294).
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