You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Philippe Marschall (JIRA)" <ji...@codehaus.org> on 2010/05/04 21:14:12 UTC

[jira] Created: (MSOURCES-53) defaultManifestFile should not be readonly

defaultManifestFile should not be readonly
------------------------------------------

                 Key: MSOURCES-53
                 URL: http://jira.codehaus.org/browse/MSOURCES-53
             Project: Maven 2.x Source Plugin
          Issue Type: Improvement
    Affects Versions: 2.1.1
            Reporter: Philippe Marschall
            Priority: Minor
         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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MSOURCES-53) defaultManifestFile should not be readonly

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.

     [ https://jira.codehaus.org/browse/MSOURCES-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MSOURCES-53.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2
         Assignee: Olivier Lamy
    
> defaultManifestFile should not be readonly
> ------------------------------------------
>
>                 Key: MSOURCES-53
>                 URL: https://jira.codehaus.org/browse/MSOURCES-53
>             Project: Maven 2.x Source Plugin
>          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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira