Difference between revisions of "Plugin refactor log"

Revision as of 20:42, 28 November 2006

November 28, 2006

Plugin refactoring is almost complete! The following plugins have been obsoleted:

org.eclipse.jst.jsf.contentassist.el (moved to core and ui)

org.eclipse.jst.jsf.context.symbol (moved to common)

org.eclipse.jst.jsf.designtime (moved to core and standard.tagsupport)

org.eclipse.jst.jsf.facesconfig.common (moved to common.ui)

org.eclipse.jst.jsf.facesconfig.edit (moved to facesconfig)

org.eclipse.jst.jsf.metadataprocessors (moved to core and standard.tagsupport)

org.eclipse.jst.jsf.taglibprocessing (moved to core and standard.tagsupport)

org.eclipse.jst.jsf.validation.el (moved to core and ui)

org.eclipse.jst.pagedesigner.common (moved to common.ui)

Obsoleted plugins have been intentionally broken at HEAD to prevent future use. Note that some meta-data and extension point names that are bundle id relative have also changed.

The following new plugins have been created out of the merged plugins:

org.eclipse.jst.jsf.common.ui -- merges all the Sybase "common" plugin code for faces config and pagedesigner

org.eclipse.jst.jsf.standard.tagsupport -- a new plugin containing "out-of-the-box" tag support.

A running log of the refactoring is here: http://wiki.eclipse.org/index.php/Plugin_refactor_log.

The list of functional (non-test, non-doc) plugins is now:

org.eclipse.jst.jsf.common (non-JSF specific common logic)

org.eclipse.jst.jsf.common.ui (shared UI)

org.eclipse.jst.jsf.core (framework core)

org.eclipse.jst.jsf.facesconfig (faces-config.xml EMF model, translators and .Edit providers)

org.eclipse.jst.jsf.facesconfig.ui (faces-config.xml visual editor)

org.eclipse.jst.jsf.standard.tagsupport (default tag support for f and h libraries)

org.eclipse.jst.jsf.ui (exemplary UI)

org.eclipse.jst.pagedesigner (visual page designer core)

org.eclipse.jst.pagedesigner.jsp.core (JSP support for VPD)

org.eclipse.jst.pagedesigner.jsf.ui (JSF support for VPD).

November 21, 2006

- moved org.eclipse.jst.jsf.core.internal.types package to org.eclipse.jst.jsf.common plugin. Renamed package to org.eclipse.jst.jsf.common.internal.types.

- moved package org.eclipse.jst.jsf.core.internal.provisional.util to org.eclipse.jst.jsf.common plugin. Renamed package to org.eclipse.jst.jsf.common.internal.provisional.util

November 20, 2006

In the continued effort to refactor and reduce our JSF plugins, the following actions have been taken:

- the JSF code and test plugins have been branched on the R1_5_maintenance path. All future maintenance and patch work must be committed against this branch if it applies to the 1.5.x release stream.

- the JSF plugins have been updated to merge the following plugins:

org.eclipse.jst.jsf.contentmodel.annotations org.eclipse.jst.jsf.context org.eclipse.jst.jsf.context.structureddocument org.eclipse.jst.jsf.context.resolver org.eclipse.jst.jsf.context.resolver.structureddocument

into a new plugin: org.eclipse.jst.jsf.common. Furthermore, the above plugins have been *intentionally broken* at HEAD. These plugins should no longer be used for ongoing development in the WTP 2.0 build stream.

November 8, 2006

Please be advised that as part of plugin refactoring, the following plugins will soon be obsolete at HEAD (unreleased):

org.eclipse.jst.jsf.context org.eclipse.jst.jsf.context.resolver org.eclipse.jst.jsf.context.structureddocument org.eclipse.jst.jsf.context.resolver.structureddocument org.eclipse.jst.jsf.contentmodel.annotations

All code and API will be preserved in a new common plugin called: org.eclipse.jst.jsf.common.

Impact:

Once these changes are promoted to release (no sooner than M3):

1) Any adopter plugins currently relying any of these plugins will need to remove Manifest.MF references to them and add one for org.eclipse.jst.jsf.common. Package names will not be changed.

2) Any adopters using the org.eclipse.jst.jsf.contentmodel.annotations.annotationFiles extension point must change the name to: org.eclipse.jst.jsf.common.annotationsFiles.

Another message will be sent on this mailing list once the change has been committed to CVS. Please send any questions or concerns to this mailing list.

Regards,

Cameron