Community
Participate
Working Groups
Some projects and classes still refer to the old metamodel : org.eclipse.jwt.transformations.properties.ExtractPropertiesService -> patching it Some have bad external dependencies : jwt-transformations-xslt-tools depends on Xalan 2.7.1, but Xalan 2.7.1 is not available if branch v2_7 checked out from orbit because it provides 2.7.0.qualifier -> putting 2.7.0 so it accepts any 2.7.* version jwt-we-sample-registereddynamicaspect misses the EMF dependancy -> adding it Some have bad inner dependencies : jwt-wam-monitoring depends on jwt-wam-api 1.0, but there is no such version -> upgrading jwt-wam-api to 1.1.0.qualifier because of recent improvements such as ProcessQuery that will be released in JWT 1.1 (see related bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=329362 , where we also export its package in the manifest) Some refer to old, since refactored code : jwt-view/org.eclipse.jwt.weview.gui.AppWindow refers to obsolete org.eclipse.jwt.we.misc.logging.Level and org.eclipse.jwt.we.misc.views.ViewResourceManager -> for Chris to see if it has to be patched, or deleted altogether if obsolete
org.eclipse.jwt.transformations.xslt.tools.XSLTProcessor can't access the method SAXParserFactoryImpl.newInstance() -> replacing it with SAXParserFactory.newInstance("org.apache.xerces.jaxp.SAXParserFactoryImpl", null);
All OK, only remaining : Chris to look at jwt-view.
jwt-view is an old part of JWT that should probably be obsoleted. For now, I've documented it as OBSOLETE in the SVN layout at http://wiki.eclipse.org/JWT_SVN#we-plugins . Maybe we should delete it, or move it to an Archive folder later.
