Enhancement: add OSGi meta data to jar file manifests

[GoogleCodeExporter]

Please add OSGi meta data (Bundle headers) to the manifests of your jar files. 

Original issue reported on code.google.com by thilopl...@googlemail.com on 19 Jun 2009 at 8:22

[GoogleCodeExporter]

Hi There,

I've updated the build system to use bnd [1] to generate osgi artefacts for 
these
jars. I've attached the modified build system, and if its suitable to commit to 
the
code, please do so. bnd should be license compatible for it to be available as 
part
of the download.

In this build file, osgi jars are auto generated into lib/ogsi. I haven't 
tested that
all the code is osgi safe. 

[1] http://www.aqute.biz/Code/Bnd

Original comment by adrian.s...@gmail.com on 16 Jul 2009 at 9:33

Attachments:

• build-src.xml

[GoogleCodeExporter]

Adrian, Thanks for the patch.  We are in the process of revamping the library 
to a
new data model and in the process updating the build configuration as well (for
version 2.0 of the library).  We will add this as part of that general effort. 

Original comment by vbarat...@gmail.com on 23 Jul 2009 at 2:49

• Changed state: Accepted

[GoogleCodeExporter]

I've tried the zip download at 
http://code.google.com/p/gdata-java-client/downloads/list and the Maven-ized 
version (thanks Pascal!) at http://code.google.com/p/mandubian-mvn/

Neither includes any OSGi manifest generation.  I see the status of this issue 
has been "Accepted" for 1.5 years now.  Is this going to happen any time soon?  
Or would a local code fork be more appropriate?

Original comment by watermel...@gmail.com on 23 Jan 2011 at 3:42