Community
Participate
Working Groups
As Xerces was first put into Orbit, I did the "quick and dirty" approach of requiring and re-exporting it's companion bundles. This deserves more thought. At a minimum, we should spec version ranges (after studying xerces history and policies a bit more). Require-Bundle: system.bundle, org.w3c.dom;visibility:=reexport, org.apache.xml.resolver;visibility:=reexport
Note to self: another improvement might be to assign some eclipse access rules so that things in XercesImpl were "discouraged" but, naturally, the true API's in xml-apis (that is, the org.w3c.dom and javax.xml were not discouraged.
Required bundles are located in OSGi frameworks using Bundle-SymbolicName entry in the MANIFEST files. org.eclipse.osgi is the Bundle-Symbolic-Name for the equinox framework. Why the dependency on the system bundle is not specified as org.eclipse.osgi instead of system.bundle?
Jose, sorry for the long delay in responding. I used system.bundle since it was recommend by Tom Watson in another bug (bug 167695). To quote his explanation, including my quote with similar question :) >> What about the change to xerces bundle ... ? >> system.bundle? I've not heard of that before ... .is that something I should >> know about? Or, is it "short hand" for something else that I am missing? >The system.bundle symbolic name is an alias for the symbolic name of the system >bundle (org.eclipse.osgi). In this case you are only requiring it so that you >get the public API that is exported from the VM Execution Environment profile. >You do not care which framework implementation you get wired to, that is why I >recommend system.bundle vs org.eclipse.osgi.
Doing a mass "reset to default assignee" of 21 bugs to help make clear it will (very likely) not be me working on things I had previously planned to work on. I hope this will help prevent the bugs from "getting lost" in other people's queries. Feel free to "take" a bug if appropriate.
