You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Amitkumar Inkar (JIRA)" <ji...@codehaus.org> on 2008/07/23 14:14:26 UTC
[jira] Commented: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142869#action_142869 ]
Amitkumar Inkar commented on MECLIPSE-386:
------------------------------------------
Hi I am facing the same issue and not able to fins a work around. Is there a possibîlity to configure plexus-archier to use a different defaultmanifest.mf file as the Archiver-Version entry is coming from that file itself
> Modified MANIFEST.MF file for eclipse jars packaged from folders with eclipse:to-maven
> --------------------------------------------------------------------------------------
>
> Key: MECLIPSE-386
> URL: http://jira.codehaus.org/browse/MECLIPSE-386
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: OSGi, Manifest, PDE support
> Reporter: Pierre-Arnaud Marcelot
>
> The MANIFEST.MF file of some Eclipse jars deployed on the http://repo1.maven.org/maven2 repository using the eclipse:to-maven goal has been modified.
> When using these jars within Eclipse, the jar signing verification fails.
> The line "Archiver-Version : Plexus Archiver" has been added to the original MANIFEST.MF.
> This issue seems to apply only on Eclipse jars that are packaged as folder in the 'plugins' folder of an Eclipse installation.
> The following (at least) packages fails verification with eclipse:
> * org.eclipse.core.runtime.compatibility.registry plugin, version 3.2.100-v20070316
> * org.eclipse.ui.workbench.compatibility plugin, version 3.2.0.I20070319-0010
> For instance in the org.eclipse.core.runtime.compatibility.registry plugin, version 3.2.100-v20070316 plugin, not only the MANIFEST.MF file is modified in the way I described earlier, but the SHA1-Digest of the runtime_registry_compatibilty.jar has been changed too (and thus the file itself).
--
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