Community
Participate
Working Groups
Extracted from bug 175284 All of the repack (pack200 -r), unpack200, and jarsigner tools leave their results in slightly different formats with respect to the compression of the resulting jar (mostly around whether crc & size information goes before or after a record entry). This may depend on the OS & VM used. Because of this, when nesting jars inside of something that is being signed, the jarprocessor performs a "normalization" step on the nested jars to ensure that they are always the same. It appears that by skipping the signing on the nested jars, we are also skipping one of the normalization steps resulting in nested jars whose contents are identical, but where the jars themselves have different bytes because of the crc & size info moving around.
Raising the importance - Welcome needs this so that we can test layering (installing Platform, then JDT and PDE).
Fixed in head. This affects the jarprocessor.jar that is used to do the conditioning, signing and packing. I tested with pde.build excluding the nested pdebuild-ant.jar from signing. I did condition/sign, pack, unpack, verify on windows and linux. I also did condition/sign, pack on linux, unpack and verify on windows.
