[
https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574723#comment-14574723
]
Carsten Ziegeler commented on MJAR-193:
---------------------------------------
Right, the bundle plugin today creates the jar file, one of the reasons (not
the only one) for doing so, was that it's not possible to pass information to
the jar plugin. The way the bundle plugin works today is wrong as it does a lot
of things (resource processing, packaging etc.) in a single phase - which is
not the maven way. In the meantime, a new bundle plugin has been developed (
http://njbartlett.name/2015/03/27/announcing-bnd-maven-plugin.html ) which
follows the maven phases and leaves the jar generation to the jar plugin. but
it comes with the problem mentioned in this issue
> 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)
