Jump to: navigation, search

Difference between revisions of "ATF/BuildingJSDT"

< ATF
(New page: JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0 *org.eclipse.wst.jsdt.web....)
 
Line 1: Line 1:
 +
JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0
 +
 +
*org.eclipse.wst.jsdt.web.support.jsp
 +
*org.eclipse.wst.jsdt.web.ui
 +
 +
The following changes will be made
 +
 +
'''org.eclipse.wst.jsdt.web.support.jsp'''
 +
 +
*The plugin org.eclipse.wst.jsdt.web.support.jsp is no longer used in WTP 3.0. the plugins will be reverted back to run against WTP 2.0.
 +
 +
'''org.eclipse.wst.jsdt.web.ui'''
 +
 +
*The changes in org.eclipse.wst.jsdt.web.ui that were removed/changed will be moved into org.eclipse.atf.compatibility.jsdt. The original plan was to use a previous version of for the plugin.xml file. This is no longer possible because of class renaming done in JSDT.
 +
 +
*There is one outstanding issue is that the plugins.xml in org.eclipse.wst.jsdt.web.ui  has one element that doesn't  exist in WTP 2.0. The manifest compiler will be set to ignore the error on the build. As I remember this was used in the pervious release because of a number of undefined extension points in earlier versions of JSDT.
 +
 +
------------------
 +
 +
Because of changes in JSDT, the original proposal below will not obsolete
 +
 
JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0
 
JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0
  

Revision as of 16:40, 18 February 2008

JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0

  • org.eclipse.wst.jsdt.web.support.jsp
  • org.eclipse.wst.jsdt.web.ui

The following changes will be made

org.eclipse.wst.jsdt.web.support.jsp

  • The plugin org.eclipse.wst.jsdt.web.support.jsp is no longer used in WTP 3.0. the plugins will be reverted back to run against WTP 2.0.

org.eclipse.wst.jsdt.web.ui

  • The changes in org.eclipse.wst.jsdt.web.ui that were removed/changed will be moved into org.eclipse.atf.compatibility.jsdt. The original plan was to use a previous version of for the plugin.xml file. This is no longer possible because of class renaming done in JSDT.
  • There is one outstanding issue is that the plugins.xml in org.eclipse.wst.jsdt.web.ui has one element that doesn't exist in WTP 2.0. The manifest compiler will be set to ignore the error on the build. As I remember this was used in the pervious release because of a number of undefined extension points in earlier versions of JSDT.

Because of changes in JSDT, the original proposal below will not obsolete

JSDT is moving into WTP 3.0. The latest versions of JSDT is not longer compatible with WTP 2.0. The following JSDT plugins are no longer compatible with WTP 2.0

  • org.eclipse.wst.jsdt.web.support.jsp
  • org.eclipse.wst.jsdt.web.ui

The area that is not compatible is the plugin.xml files for the two plugins. A version of the plugin.xml that work with WTP have been tag with the id v200711071635. The following process will be followed to create a build.

  • The version for JSDT will be checkout of the head.
    • The plugin.xml for the org.eclipse.wst.jsdt.web.support.jsp and org.eclipse.wst.jsdt.web.ui will be switch to the tag **version v200711071635.
    • The checkout version of JSDT will now be tag with the build id.
    • There are no plans to automate this process, since the problem goes away when ATF moves to WTP 3.0.