[
http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142884#action_142884
]
amitinkar edited comment on MECLIPSE-386 at 7/23/08 9:29 AM:
-------------------------------------------------------------------
Hi
I managed to find a temporary solution for this. I changed the
defaultManifest.mf file inside plexus-archiver-1.0-alpha-7.jar file as below.
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
This helped me to get rid of the extra line Archiver-Version : Plexus Archiver
from the artifacts that are created using the eclipse-to-maven plugin.
This has resolved the verification failure from Eclipse.
This is just a workaround but I need a permanant solution.
was (Author: amitinkar):
Hi
I managed to find a temporary solution for this. I change the
defaultManifest.mf file inside plexus-archiver-1.0-alpha-7.jar file as below.
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
This helped me to get rid of the extra line Archiver-Version : Plexus Archiver
from the artifacts that are created using the eclipse-to-maven plugin.
This has resolved the verification failure from Eclipse.
This is just a workaround but I need a permanant solution.
> 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
