[
https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576281#comment-14576281
]
Karl Heinz Marbaise commented on MJAR-193:
------------------------------------------
What comes into my mind was: Have you tested if you could use the configuration
like this where you need to create the appropriate MANIFEST.MF file at
{{target/classes/META-INF/MANIFEST.MF}} and it should be picked up without any
modification...
{code}
<plugins>
<plugin>
<...>maven-jar-plugin</...
<configuration>
<useDefaultManifestFile>true</useDefaultManifestFile>
</configuration>
{code}
> 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)
