Details
-
Feature Request
-
Resolution: Done
-
Blocker
-
3.3.0.Beta3
-
None
Description
Juno is coming - This year, lets see if we can stay compatible. There should be a compatibility layer so unless we use changed internal API's we should be fine.
If you have a plugin that does not compile/work then we should investigate what options we got - trying to avoid having to maintain two forks!
Eclipse migration tips: http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.platform.doc.isv/porting/3.8/incompatibilities.html?revision=1.1&view=co
(not sure that being empty can be all true)
WTP help for old friends: http://wiki.eclipse.org/New_Help_for_Old_Friends_VII
See JBIDE-8624 for last years Indigo move.
Please link related Juno to this issue and if we find issues please outline the fix and if relevant relate eclipse bugzilla references.
Attachments
Issue Links
- blocks
-
JBDS-2244 Should JBDS 6 use the new Eclipse 4.2 skin or continue to look like JBDS 5 (Eclipse 3.7)
- Closed
-
JBDS-2236 Bump feature and plugin versions to new baselines for Juno
- Closed
-
JBIDE-12239 Migrate Central module to eclipse Juno
- Closed
-
JBIDE-12240 Migrate Openshift to eclipse Juno
- Closed
- is blocked by
-
JBIDE-11469 build Juno target platforms (Eclipse 4.2.0/3.8.0)
- Closed
- relates to
-
JBIDE-11469 build Juno target platforms (Eclipse 4.2.0/3.8.0)
- Closed
-
JBIDE-12262 org.jboss.tools.jsf.vpe.jsf.test failure
- Closed
-
JBIDE-12263 org.jboss.tools.jsf.vpe.seam.test failure
- Closed
-
JBIDE-12268 org.jboss.tools.seam.core.test failure
- Closed
-
JBIDE-12277 Some tests get aborted and return error 134
- Closed
-
JBIDE-12278 maven-antrun-plugin fails on Central job
- Closed