[
https://issues.apache.org/jira/browse/FELIX-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050493#comment-13050493
]
Stuart McCulloch commented on FELIX-2910:
-----------------------------------------
Note that I get the same error about the Name sections with 2.2.0, so I can't
see how this was working with 2.2.0
If you have a test project (pom+instructions) that did work with 2.2.0 please
attach it to this issue, in case there is anything else we can do. But for now
the easiest way to merge manifests is to take advantage of the above
bundleplugin feature (where it looks at the maven-jar-plugin configuration and
merges with that). Any other change would require a change to bnd, but as I
mentioned above the explicit error message does suggest that bnd deliberately
disallows including files with "Name" sections...
> Regression: maven-bundle-plugin 2.3.4 is ignoring individual entries in
> custom MANIFEST.MF
> ------------------------------------------------------------------------------------------
>
> Key: FELIX-2910
> URL: https://issues.apache.org/jira/browse/FELIX-2910
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.4
> Reporter: Jörg Waßmer
> Assignee: Stuart McCulloch
> Priority: Critical
>
> I tell the plugin to use a custom manifest via the <_include> option.
> Version 2.2.0 of the plugin correctly copies all entries from the specified
> manifest to the one generated by the plugin.
> Version 2.3.4 is skipping all manifest entries that are related to individual
> packages and classes.
> For example:
> Name: foo/bar
> Sealed: true
> Name: foo/bar/Bean.class
> Java-Bean: true
> Name: foo/bar/Bean2.class
> Java-Bean: true
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
