[
https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265235#comment-15265235
]
Karl Heinz Marbaise commented on MJAR-193:
------------------------------------------
First it is important to say that with version 3.0.0 of maven-jar-plugin the
option via {{useDefaultManifestFile}} will not exist anymore. The second
options via manifestFile will work of course. Using the project context might
influence other parts of the build which should be prevented. May be you can
show an example of the code you use ? What i can think of is having an external
manifest-merge.mf file which might be merged with the current existing one...?
But i need think hard about that...
> Allow other mojos to contribute to the manifest
> -----------------------------------------------
>
> Key: MJAR-193
> URL: https://issues.apache.org/jira/browse/MJAR-193
> Project: Maven JAR Plugin
> Issue Type: Improvement
> Reporter: Carsten Ziegeler
> Fix For: waiting-for-feedback
>
>
> It would be great to have a programmatic way to add entries to the manifest
> from other mojos. The most important client of such a way would be the maven
> bundle plugin (from the Apache Felix project) that calculates additional
> headers for OSGi bundles. Right now, that bundle does not only do the
> calculation but generates the jar file as well.
> While a workaround would be to let the bundle plugin generate the full
> manifest and configure the jar plugin to use it, this is not very elegant.
> Passing down a map of manifest entries from one mojo to the jar plugin would
> solve this in a much better way.
> And I could imagine that other mojos/plugins might benefit for this as well.
> This would be a simple but very convenient enhancement to the plugin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
