[
https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071985#comment-17071985
]
Raymond Augé commented on MJAR-193:
-----------------------------------
I agree with [~rfscholte]. This is an issue that cannot be solved without some
contract being added either to maven-jar-plugin, but more likely to Archiver.
The requirement is essentially to be able for some plugin (in a phase earlier
than the jar plugin; package) to indicate the manifest file to use. But since
the manifest is actually handled by the plexus archiver, the archiver may also
need to support this. However, I'm unclear what is the best strategy for
reliable communication across plugins especially given possibly multiple (jar)
plugin executions. [~rfscholte] any ideas for such communication/forwarding of
information; note that the idea is not to require the maven-jar-plugin to be
configured beyond applying it.
> 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
> Priority: Major
> 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
(v8.3.4#803005)
