[
https://issues.jboss.org/browse/JBIDE-13428?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13428:
------------------------------------
Please provide migration points so I know what's changing and from where it should now
be sourced:
features/plugins namespaces
* before: org.jboss.tools.foo
* after: org.eclipse.bar.foo
URLs
* before:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.1_trunk....
* after:
http://download.eclipse.org/something/something/something/
I'm assuming that rather than this stuff being pulled from
Eclipse.org into our
component builds directly, it will instead move into the Target Platform(s) and be sourced
from there when building components / aggregates / product. And, like everything else we
mirror from
eclipse.org to
download.jboss.org/jbosstools/updates/requirements/ these will
be added to the increasingly large list of extensions hosted here:
http://download.jboss.org/jbosstools/updates/m2e-extensions/
Or are they simply going to be PART of the m2e-wtp update site directly? (That would be
simpler and I'd be happier.) :)
Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT/JBDS update
sites, installers
---------------------------------------------------------------------------------------
Key: JBIDE-13428
URL:
https://issues.jboss.org/browse/JBIDE-13428
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha1, 4.0.x
The JBoss Maven JPA, JSF, JAX-RS being migrated over m2e-wtp, the plugins and features
have been removed from the git repo.
We need to make sure the the JBT/JBDS update sites, installers are curated as well.
--
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