The OSGi build has been redone with an approximation to the version information.
The maven-bundle-plugin version was reset back to 2.1.0, which adds a version number for all packages in the export list. This approach is not in line with the OSGi model, which wants each "package" to have its own version, but it is probably enough to get going. Tommaso, it would be good if you could update from trunk and rebuild the OSGi plugins and retest. -Marshall On 8/15/2011 10:21 AM, Marshall Schor wrote: > Tommaso has done some testing, and found that the MANIFEST files don't contain > the versions exported so that other bundles (the ones 'using' the annotators) > which declare to import packages of a certain version cannot be started > correctly even if the annotator bundle was correctly started: > ... > [ 128] [Active ] [ 5] UIMA Annotator: AlchemyAPIAnnotator > (2.3.1.SNAPSHOT) > [ 129] [Active ] [ 5] UIMA Annotator: OpenCalaisAnnotator > (2.3.1.SNAPSHOT) > [ 131] [Active ] [ 5] Clerezza - Apache UIMA related ontologies > (0.1.0.incubating-SNAPSHOT) > [ 132] [Active ] [ 5] UIMA Eclipse: uimaj-ep-runtime (2.3.1) > ... > start file:/Users/tommaso/Documents/uima.utils-0.1-incubating-SNAPSHOT.jar > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.clerezza.uima.utils [135]: Unable to resolve 135.0: missing > requirement [135.0] package; > (&(package=org.apache.uima.alchemy.ts.categorization)(version>=2.3.0)) > > If I run 'inspect package capability <bundleid>' for OpenCalaisAnnotator I > get: > inspect package capability 129 > org.apache.uima.OpenCalaisAnnotator [129] exports packages: > ----------------------------------------------------------- > org.apache.uima.annotator.calais; version=0.0.0 > org.apache.uima.calais; version=0.0.0 > > -Marshall (copying part of note from Tommaso) >
