Modified MANIFEST.MF file for eclipse jars packaged from folders with eclipse:to-maven

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: OSGi, Manifest, PDE support
  • Labels:
    None

Description

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).

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. PLXCOMP-177 JarArchiver generates lines longer than 72 bytes in MANIFEST.MF

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Amitkumar Inkar added a comment -

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

Show
Amitkumar Inkar added a comment - 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
Hide
Permalink
Amitkumar Inkar added a comment - - edited

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.

Show
Amitkumar Inkar added a comment - - edited 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.
Hide
Permalink
David GAY added a comment -

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.

Show
David GAY added a comment - 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.
Hide
Permalink
Petar Velikov added a comment - - edited

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)

Show
Petar Velikov added a comment - - edited 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)

People

  • Assignee:
    Unassigned
    Reporter:
    Pierre-Arnaud Marcelot
Vote (7)
Watch (8)

Dates

  • Created:
    Updated: