[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-139) Ability to generate OSGi bundle headers
[
https://issues.jboss.org/browse/SHRINKWRAP-139?page=com.atlassian.jira.pl...
]
John Ament commented on SHRINKWRAP-139:
---------------------------------------
rawr zombie jira ticket update looming.
So, was thinking about this with regard to some fuse/servicemix stuff I'm playing with
currently. Having a descriptor to do this makes the most sense. A BundleArchive would
only support one thing (e.g. a JAR file w/ manifest), not necessarily a WAR file with that
manifest. I don't think introducing a bundle archive fixes that stuff.
I do think creating an OSGIDescriptor/OSGIManifest, and potentially a BlueprintDescriptor
would help. While right now the descriptors are all reverse engineered based on XSDs,
that doesn't mean we can't have one that's not based on an XSD (and as a
result, directly coded).
Ability to generate OSGi bundle headers
---------------------------------------
Key: SHRINKWRAP-139
URL: https://issues.jboss.org/browse/SHRINKWRAP-139
Project: ShrinkWrap
Issue Type: Feature Request
Reporter: Pete Muir
As we control the classpath generating an OSGi bundle header should be straightforward.
Introducing an API to customize it is perhaps harder, but should be possible.
May want to look at delegating to BND (http://www.aqute.biz/Code/Bnd).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira