[
https://issues.apache.org/jira/browse/MSOURCES-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959433#comment-17959433
]
Matthias Bünger commented on MSOURCES-53:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-source-plugin#129|https://github.com/apache/maven-source-plugin/issues/129].
> defaultManifestFile should not be readonly
> ------------------------------------------
>
> Key: MSOURCES-53
> URL: https://issues.apache.org/jira/browse/MSOURCES-53
> Project: Maven Source Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.1.1
> Reporter: Philippe Marschall
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 2.2
>
> Attachments: maven-source-plugin.patch
>
>
> The location of the default manifest file is hardcoded to
> {code}${project.build.outputDirectory}/META-INF/MANIFEST.MF{code} with no
> possibility to change it (@readonly). We have a case where we need to have a
> different manifest in the source jar than in the binary jar. Currently we can
> not do this with the Maven Source Plugin because we can't make it use a
> different manifest.
> The reason we need to have a different manifest in the source jar than the
> binary jar is that we generate manifests for OSGi bundles. The source jar
> needs to be a so called source bundle which means having different manifest
> headers. Unfortunately the logic for generating those headers is a bit
> complicated so it can't be done with a MavenArchiveConfiguration but has to
> be done with a custom plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
