OSGi support

[aborg0]

It would be nice to be able to use jopt-simple from OSGi environments. As it has no compile dependencies, it would mean that a symbolic name, version and the exported packages need to be added to the MANIFEST.MF file.

[pholser]

@aborg0 Thanks for your interest! Will you have a look at the pull req I've issued regarding this? I want to make sure that the build (using maven-bundle-plugin) will produce a JAR file with the OSGi metadata you're looking for.

[pholser]

Latest 4.8 snapshot at oss.sonatype.org should have this change.

[boly38]

@pholser thanks for your feedback; 4.8 snapshot from oss sonatype is usefull for me!

I know this is so so minor, but while adding OSGi directives in MANIFEST.MF
could you finalize this by adding the following

 Bundle-Vendor

(One of my components parse each bundle to get name and vendor attributes)
regards

[pholser]

@boly38 Sure thing. Will probably use "JOpt Simple" as the value.

[boly38]

^^

[pholser]

@boly38 Latest 4.8 snapshot at oss.sonatype.org should have the Bundle-Vendor set.

[boly38]

excellent. thanks

[aborg0]

@pholser do you have an estimate for the next release date? It would be nice to use jopt-simple as a released OSGi dependency. (We will reach the feature freeze next week, but if the jopt-simple will be released soon, we would make an exception.)
Thanks.

[pholser]

@aborg0 Releases of JOpt Simple are somewhat irregular. I tend to wait until a significant number of features has accumulated before declaring a new point release. It seems that the differences between 4.7 and what would be 4.8 are the OSGi metadata and i18n of exception messaging.

I think perhaps I will declare 4.8 beta 1, and let these changes be vetted. Sound good? If things look pretty good after a week or two with 4.8 beta 1 in the wild, I'll declare 4.8.

[aborg0]

@pholser Thanks, that sounds good.

[pholser]

@aborg0 @boly38 4.8 beta 1 should be available on GitHub right now; in Maven central as soon as Sonatype syncs it.

[aborg0]

@pholser Thanks, it seems to be perfect from my point of view.
(I have included it in my (osgi source bundles project)[https://github.com/aborg0/osgi_source_bundles], so that way it is easier to use from an OSGi environment, like eclipse. If you prefer, you can add a separate module for the OSGi sources. The howto is here: http://codeiseasy.wordpress.com/2012/07/22/convert-a-maven-source-bundle-to-an-eclipse-source-bundle/ not sure how well it works for Sonatype/maven central releases.)