[
https://issues.apache.org/jira/browse/FELIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated FELIX-3994:
----------------------------------
Attachment: FELIX-3994.diff
Here's a patch that adds Merge-Headers instruction that be filled with a list
of BND compatible instructions (wildcards, negations, etc.). Patch only applies
when this header exists, otherwise full backwards compatibility is preserved.
There a two places where merge occurs when it's requested. First one is when
BND generated manifest is overlaid with headers coming from maven archiver's
<artifact> tag. This is might be interesting when external manifest file is
used and the merged manifest is supposed to go inside the artifact. The second
one only applies only to the manifest that is written outside artifact. Here
the pre-existing manifest file is overlaid with artifact's manifest. This is
handy with PDE.
> Optional merging of duplicate manifest headers
> ----------------------------------------------
>
> Key: FELIX-3994
> URL: https://issues.apache.org/jira/browse/FELIX-3994
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Reporter: Tuomas Kiviaho
> Priority: Minor
> Attachments: FELIX-3994.diff
>
>
> Bundle plugin seems to always overwrite exported manifest. There are
> currently several other ways of merging manifest headers together but none of
> them can merge duplicated headers back to one or omit unwanted/uninteresting
> headers altogether.
> [Archiver|http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html]
> can already be used pass headers to BND process but what I'm after is to
> only have an impact what is written out to the manifest location at the end
> and not tamper with the produced artifact itself.
> The idea is to be able to print out project artifact's manifest for Eclipse
> PDE and later on selectively overlay it with test artifact's manifest so that
> PDE sees simultaneously information from both artifacts excluding test-only
> headers such as {{Fragment-Host}} and those starting with {{Bundle-}}
--
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