Folks,
The plugin version id changes were delayed due to the schedule change
of WTP 3.2 M1 (this release would have occurred during our shutdown
period). Hopefully this gave everyone enough time to react to these,
because I will be releasing these updates later today. Once again, please
use https://bugs.eclipse.org/bugs/show_bug.cgi?id=269281 for any discussion
about this.
Please let me know if you have any comments/questions/concerns.
- Carl Anderson
WTP programmer
Carl
Anderson/Raleigh/
i...@ibmus To
Sent by: "General discussion of project-wide
wtp-dev-boun...@e or architectural issues."
clipse.org <[email protected]>
cc
07/30/2009 12:53 Subject
PM [wtp-dev] Upcoming WST plugin
version id changes
Please respond to
"General
discussion of
project-wide or
architectural
issues."
<wtp-...@eclipse.
org>
Folks,
In WTP 3,2, as part of https://bugs.eclipse.org/bugs/show_bug.cgi?id=269281
, we are refactoring the classes that WST uses out of org.eclipse.jem.util
and into various WST plugins. (The jem.util classes are converted to
wrappers and are deprecated. Their WST replacements have the same name and
are referenced by fully qualified name in the @deprecated tag.) These
plugins will all have their minor level bumped, since this is a big change.
(Note that org.eclipse.jem.util will still have the same API and extension
points and should work just the same as it does today- however, it will be
moved out of org.eclipse.wst.common_core.feature and into
org.eclipse.jst.web_core.feature. That means that plugins above the WST
layer should still be able to access everything just as they do today.)
As is listed in the bug, here are the new plugin version ids:
org.eclipse.jem.util 2.1.0
org.eclipse.wst.common.core 1.2.0
org.eclipse.wst.common.emf 1.2.0
org.eclipse.wst.common.emfworkbench.integration 1.2.0
org.eclipse.wst.common.frameworks 1.2.0
org.eclipse.wst.common.frameworks.ui 1.2.0
org.eclipse.wst.common.modulecore 1.2.0
I plan on committing these plugin version changes right after the WTP 3.2
declare on August 6th. Also, while you are updating these ranges, I would
highly recommend removing any dependency on org.eclipse.jem.util (including
extension points, as these are also being moved down) and instead use the
appropriate WST class/extension point. (Those changes will be committed
this week, after the WTP 3.2 declare. The bug will be updated as the
various parts are put in.) Our long-term plan is to make
org.eclipse.jem.util exactly what it should be - a utility plugin for JEM
(and only JEM). However, as per our API contract, for the WTP 3.2 release,
the jem.util API is remaining intact... but will be deprecated.
Please let me know if you have any comments/questions/concerns.
FWIW,
- Carl Anderson
WTP programmer_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
<<inline: graycol.gif>>
<<inline: pic36646.gif>>
<<inline: ecblank.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
