Community
Participate
Working Groups
Build ID: I20090611-1540 Steps To Reproduce: 1. Download GMF 2.2.0 SDK or runtime (the Galileo version) 2. Extract downloaded zip 3. Go into the plugins folder 4. Open the MANIFEST.MF file inside JAR org.w3c.dom.smil_1.0.1.v200903091627.jar. It shows: Import-Package: org.w3c.dom,org.w3c.dom.events;version="[3.0.0,4.0.0)" 5. Open Open the MANIFEST.MF file inside JAR javax.xml_1.3.4.v200902170245.jar It shows: Export-Package: ... org.w3c.dom.events;version="2.0" ... More information: We are using GMF SVG plugin for exporting a diagram to SVG. After updating to Eclipse 3.5 Galileo, our diagram editor plug-in did not start (in OSGI terms, it was not resolved). Our diagram editor plugin has a dependency on GMF's org.w3c.svg plug-in, which on its turn depends on plug-in org.w3c.dom.smil. This plug-in cannot be resolved since it wants version 3 of the org.w3c.dom.events package. The javax_xml plug-in supplied by the 2.2.0 release of GMF, however, only exposes version 2.0 of that package. See attached OSGI console log for more information on the unresolved dependencies.
Created attachment 140684 [details] OSGI console log
The intent for GMF 2.2 was that we still depend on the same Batik 1.6 toolkit that we used in GMF 2.1. We did verify save as SVG as well as having SVG images on the diagram and both still work with GMF 2.2. In my environment I have: org.w3c.css.sac_1.3.0.v200805290154.jar org.w3c.dom.events_3.0.0.draft20060413_v200905140418.jar org.w3c.dom.smil_1.0.1.v200903091627.jar org.w3c.dom.svg_1.1.0.v200806040011.jar javax.xml_1.3.4.v200902170245.jar Do you have something different?
(In reply to comment #2) > The intent for GMF 2.2 was that we still depend on the same Batik 1.6 toolkit > that we used in GMF 2.1. > > We did verify save as SVG as well as having SVG images on the diagram and both > still work with GMF 2.2. > > In my environment I have: > org.w3c.css.sac_1.3.0.v200805290154.jar > org.w3c.dom.events_3.0.0.draft20060413_v200905140418.jar > org.w3c.dom.smil_1.0.1.v200903091627.jar > org.w3c.dom.svg_1.1.0.v200806040011.jar > > javax.xml_1.3.4.v200902170245.jar > > Do you have something different? > We have the same versions of jars, except the product created by our headless build does NOT have plug-in org.w3c.dom.events_3.0.0.draft20060413_v200905140418. So it tries to resolve the org.w3c.dom.events package to the javax.xml_1.3.4 plug-in (which declares to have only version 2.0 of it). Our main plug-in doesn't explicitly specify a dependency on org.w3c.dom.events_3.0.0.draft20060413_v200905140418. Should we do that? Or should the headless build's dependency resolving mechanisme have picked it up? (apparently it did not).
[GMF Restructure] Bug 319140 : product GMF and component Runtime was the original product and component for this bug
I also have problems with the way the version are specified in the manifest. PDE is failing to export features that include dom.smil or apache.batik Processing inclusion from feature org.talend.designer.business_feature: Bundle org.apache.batik.bridge_1.6.0.v200912221622 failed to resolve.: Missing required plug-in org.apache.batik.css_0.0.0. Missing required plug-in org.apache.batik.dom_0.0.0. Missing required plug-in org.apache.batik.dom.svg_0.0.0. Missing required plug-in org.apache.batik.ext.awt_0.0.0. Missing required plug-in org.apache.batik.parser_0.0.0. Missing required plug-in org.apache.batik.util_0.0.0. Missing required plug-in org.apache.batik.util.gui_0.0.0. Missing required plug-in org.apache.batik.xml_0.0.0. Missing required plug-in org.w3c.dom.svg_0.0.0. This is because the manifest required plugin version is using the keyword "version" and OSGI specified "bundle-version" (may be this has change in recent OSGI, specs ? can find info on that : http://www.osgi.org/Specifications/ReferenceHeaders ). so in batik.bridge manifest instead of having Require-Bundle: org.apache.batik.css;version="[1.6.0,1.7.0)" we should have Require-Bundle: org.apache.batik.css;bundle-version="[1.6.0,1.7.0)" ^^^^^^^^^^^
