You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@codehaus.org> on 2008/02/05 11:34:28 UTC
[jira] Created: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
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
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
[jira] Commented: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
Posted by "Amitkumar Inkar (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MECLIPSE-386) Modified MANIFEST.MF
file for eclipse jars packaged from folders with eclipse:to-maven
Posted by "Petar Velikov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270438#comment-270438 ]
Petar Velikov edited comment on MECLIPSE-386 at 6/15/11 4:27 AM:
-----------------------------------------------------------------
I was able to get unmodified MANIFEST.MF files by building locally the plugin with little modification in ExplodedPlugin.java (see attached [^MECLIPSE-386.patch])
was (Author: pvelikov):
I was able to get unmodified MANIFEST.MF files by building locally the plugin with little modification in ExplodedPlugin.java (see attached MECLIPSE-386.patch)
> 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
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
Posted by "Amitkumar Inkar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142884#action_142884 ]
Amitkumar Inkar commented on MECLIPSE-386:
------------------------------------------
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
[jira] Commented: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
Posted by "David GAY (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166614#action_166614 ]
David GAY commented on MECLIPSE-386:
------------------------------------
Hi,
I think this issue also cause maven-assembly-plugin to fail with a JarVerifierException when unpacking a dependency (packaged as a folder) created by the eclipse:to-maven goal.
That's bad news for me because I'm *very near* to succed to build all my Eclipse-based product with Maven and run it simply from Hudson CI.
Too bad that the last step (build the distribution) fail.
Regards
David.
> 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
[jira] Updated: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-386:
-------------------------------------
Component/s: PDE support
OSGi, Manifest
> 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
[jira] Updated: (MECLIPSE-386) Modified MANIFEST.MF file for
eclipse jars packaged from folders with eclipse:to-maven
Posted by "Petar Velikov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petar Velikov updated MECLIPSE-386:
-----------------------------------
Attachment: MECLIPSE-386.patch
I was able to get unmodified MANIFEST.MF files by building locally the plugin with little modification in ExplodedPlugin.java (see attached MECLIPSE-386.patch)
> 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
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-386) Modified MANIFEST.MF
file for eclipse jars packaged from folders with eclipse:to-maven
Posted by "Amitkumar Inkar (JIRA)" <ji...@codehaus.org>.
[ 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