Provide OSGi meta-data for all JAR files

[GoogleCodeExporter]

Since we expect the GenXDM JAR files to be re-used in an OSGi environment, the 
JARs should have OSGi metadata.

Original issue reported on code.google.com by eric%tib...@gtempaccount.com on 3 May 2011 at 8:32

[GoogleCodeExporter]

While doing this, also worth documenting the pitfalls of using Maven and OSGi 
together, and how we got it to work.

Original comment by eric%tib...@gtempaccount.com on 3 May 2011 at 8:42

[GoogleCodeExporter]

lower priority

Original comment by aale...@gmail.com on 29 Aug 2011 at 6:43

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The workaround is to generate the OSGi metadata externally, which seems to be 
working. post-1.0 for that reason.

Original comment by aale...@gmail.com on 26 Jul 2012 at 7:56

• Added labels: Milestone-Future

[GoogleCodeExporter]

Okay. At present, there is code in /branches/osgi-project that illustrates 
this. It's nice, in a way: osgi jars, using the generate-metadata pattern so we 
don't have to do too much work. Gives us some real opportunities.

Drawbacks:

1) artifacts are renamed
2) so are jar files
3) nonetheless, we can't use the fourth version indicator (x.y.z.THISONE), 
because of maven version resolution incompatibility with OSGi
4) requires eclipse 3.7, and the updated m2e (in the eclipse tree, with 
builders and things all changed), and bndtools, for developers using the ide
5) requires the updated m2e and felix (maven-bundle-plugin) for developers 
using the command line
6) THERE WILL BE DOWNSTREAM PAIN ... because this changes all sorts of things

So ... do we want to do this, or not? Please review the code when you can, and 
provide comments here or on the mailing list.

Original comment by aale...@gmail.com on 23 Aug 2012 at 5:18

• Changed state: Started

[GoogleCodeExporter]

Done at r381. New system committed.

Original comment by aale...@gmail.com on 29 Aug 2012 at 2:01

• Changed state: Fixed