If the bundle plugin (bnd) does not automatically generate the package 
versions, I believe it's possible to explicitly generate them explicitly. I 
came across then when I was trying to get my workspace set up recently.

http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/BestPractices-BuildBundles.html

<Export-Package>
  ${project.artifactId}*;version=${project.version}
</Export-Package>

Cheers,

-- Richard

Am 16.08.2011 um 00:02 schrieb Marshall Schor:

> After spending a whole day on various experiments, I found that you can
> get the version="xxx" strings back if you back-level the version of the
> maven-bundle-plugin to 2.1.0 (it was at 2.3.4).
> 
> I'll work on that and see if I can get by with using that older version.
> 
> -Marshall
> 
> On 8/15/2011 12:14 PM, Marshall Schor wrote:
>> 
>> On 8/15/2011 11:42 AM, Marshall Schor wrote:
>>> A bit of investigation:
>>> 
>>> OSGi says that since the unit of export is a package, the package should be
>>> "versioned", by adding and then maintaining packageinfo files.  See
>>> http://www.aqute.biz/Bnd/Versioning
>>> 
>>> However, these packageinfo files are 
>> *not*
>>> used by our Eclipse plugins, which are also
>>> built using the maven-bundle-plugin, and they *have* the version 
>>> information in
>>> the Export-Package, automatically provided (from somewhere, somehow).
>>> 
>>> I tried a bunch of experiments to see if I could figure out where the bundle
>>> plugin was getting this, but couldn't find an answer.  After searching 
>>> google
>>> for this and not finding an answer, I've asked on the felix user's list :-) 
>>> ...
>>> 
>>> -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)
>>>> 

Richard Eckart de Castilho

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
[email protected] 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
------------------------------------------------------------------- 




Reply via email to