[
https://jira.jboss.org/jira/browse/JBDS-1062?page=com.atlassian.jira.plug...
]
Nick Boldt commented on JBDS-1062:
----------------------------------
While it should be crazy obvious, documentation should state somewhere that the migration
path between JBDS 2.1 and 3.0 is to NOT run update; instead a new installer is required
(though old workspace and runtimes should be usable).
If needed to explain this to users, the reason for this is that the Eclipse platform, EMF,
and WTP move in lockstep every year and adopt the newer, faster, better APIs available in
each new annual release; so while some things may work on an older platform, many do not
and thus a full install is required rather than a simple update.
Additional 3rd party plugins (eg., m2eclipse, mylyn, CDT, PDT) that users may have
installed into JBDS 2.1 may work when re-installed into 3.0, but they are unsupported by
JBDS and nothing is guaranteed. Chances are new versions (compatible with Eclipse 3.5, not
3.4) will be required.
Migration guide update from release 2.1.0 to 3.0.0GA
----------------------------------------------------
Key: JBDS-1062
URL:
https://jira.jboss.org/jira/browse/JBDS-1062
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: documentation
Affects Versions: 3.0.0.CR2-doc
Reporter: Svetlana mukhina
Assignee: OLga Chikvina
Fix For: 3.0.0.CR2-doc
Original Estimate: 6 hours
Remaining Estimate: 6 hours
Guide Update is required, contact dev team for details about compatibility issues between
two versions
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira