Quinn Stevenson created FELIX-5179:
--------------------------------------
Summary: maven-bundle-plugin incorrectly handles Bundle-Blueprint
instruction
Key: FELIX-5179
URL: https://issues.apache.org/jira/browse/FELIX-5179
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Reporter: Quinn Stevenson
When the <Bundle-Blueprint> instruction is specified, it cannot handle the
formats specified by the OSGi Blueprint specification. Further, when the
plugin incorrectly interprets the value of the instruction, it removes it from
the resulting manifest.
Examples of specification issues:
- The specification states that directories should be terminated with a '/'
character. If you do this in the Bundle-Blueprint instruction, the plugin
won't find the directory, it won't process any of the Blueprint XML files in
any directory, and it won't put the Bundle-Blueprint header in the MANIFEST.MF.
- The specification allows for wildcard in the last portion of the entry -
things like *.xml. If you put a wildcard in the Bundle-Blueprint instruction,
it behaves the same way as if the trailing '/' is appended to a directory name.
Also, the plugin re-writes the Bundle-Blueprint header to include all of the
blueprint XML files it finds. I think the plugin should leave the value alone
if it is specified. This re-write behavior is breaking my OSGi Fragment
bundles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
