Community
Participate
Working Groups
See bug 256787. We discovered a problem in the implementation of java.util.jar.Manifest that can cause it to lose the last attribute in the manifest in rare cases. We should review our use of this class and consider using ManifestElement from osgi instead.
Yes, java.util.jar.Manifest also has awful performance characteristics on signed jars: http://wiki.eclipse.org/Performance_Bloopers#JAR_signing_and_verification
A quick search in my workspace doesn't show any use of that class in p2. There are a couple of uses in OSGi but those were described by Tom yesterday in the Equinox call. (required to read all of the manifest) Can this be closed?
I found two: org.eclipse.equinox.internal.frameworkadmin.utils.Utils.basicLoadManifest(File) org.eclipse.equinox.internal.simpleconfigurator.utils.Utils.basicLoadManifest(File)
As well, the getOSGiManifest methods in those 2 utility classes use JarFile#getManifest and JarURLConnection#getManifest, both of which will end up with the same problem.
The code in simpleconfigurator does not seem to be called at all and should probably just be removed.
> The code in simpleconfigurator does not seem to be called at all and should > probably just be removed. Done.
re: comment #3. Awesome. Another case where my Java Search isn't picking up all the matches. *sigh*
*** Bug 224439 has been marked as a duplicate of this bug. ***
done