Add OSGi manifest elements

[GoogleCodeExporter]

The built jar for the javax.inject API on maven's central repo is not usable in 
an OSGi environment because it does not contain the necessary elements in the 
META-INF/MANIFEST.MF file. This file should include the following elements:

Export-Package: javax.inject;version="1.0.0"
Bundle-Version: 1.0.0
Bundle-Name: Dependency Injection for Java
Bundle-ManifestVersion: 2
Bundle-SymbolicName: javax.inject

Original issue reported on code.google.com by m...@thebishops.org on 17 Feb 2012 at 9:29

[GoogleCodeExporter]

I would also like inject to be a OSGi bundle. Should I provide a patch?

Original comment by cschneid...@gmail.com on 25 Mar 2012 at 9:28

[GoogleCodeExporter]

If you have a patch, that would be great.

Original comment by m...@thebishops.org on 25 Mar 2012 at 3:32

[GoogleCodeExporter]

Here is a patch for maven build.

Original comment by Ash2kk@gmail.com on 6 Jul 2012 at 9:05

Attachments:

• osgi.patch

[GoogleCodeExporter]

This patch looks good. 

Original comment by m...@thebishops.org on 6 Jul 2012 at 3:24

[GoogleCodeExporter]

Here's a preferred patch - similar, but doesn't require changing the maven 
packaging type, and therefore, keeps the "jar" type on the project.  This is 
not THAT big a deal in a sense, but type is metadata about a maven artifact and 
it would be good to keep it, even though "bundle" is equivalent and you'll 
still get .jar files in practice. 

Original comment by cgruber@google.com on 9 Aug 2012 at 4:32

Attachments:

• osgi.patch

[GoogleCodeExporter]

"plus 1" (google groups doesn't like + chars?) for Gruber's patch. It's better 
than my original one. 

Original comment by m...@thebishops.org on 9 Aug 2012 at 4:41

[GoogleCodeExporter]

Oh wait, I didn't submit the original patch. 

Original comment by m...@thebishops.org on 9 Aug 2012 at 4:55

[GoogleCodeExporter]

Any ETA when this patch will be integrated?

Thanks!

Original comment by mi...@raner.ws on 25 Feb 2013 at 11:58