[
https://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-386.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Modified MANIFEST.MF file for eclipse jars packaged from folders with
> eclipse:to-maven
> --------------------------------------------------------------------------------------
>
> Key: MECLIPSE-386
> URL: https://jira.codehaus.org/browse/MECLIPSE-386
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: OSGi, Manifest, PDE support
> Reporter: Pierre-Arnaud Marcelot
> Attachments: MECLIPSE-386.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
