felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quinn Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5179) maven-bundle-plugin incorrectly handles Bundle-Blueprint instruction
Date Mon, 08 Feb 2016 18:01:40 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137364#comment-15137364

Quinn Stevenson commented on FELIX-5179:

I attached at patch that fixes enough of the problem that I can proceed.  With the patch,
the plugin will correctly interrogate slash-terminated directory entries by removing the trailing
slash before it looks for directory.

The patch also disables the re-write of the Bundle-Blueprint header in the MANIFEST.MF - the
value specified in the POM is used if present.  If no value is specified in the POM, the Bundle-Blueprint
value isn't written in the MANIFEST.MF, and the default for the platform will be used.

> 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
>         Attachments: FELIX_5179.patch
> 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

View raw message