Community
Participate
Working Groups
When running just -pack on a jar, the jarprocessor is doing unnecessary work. The processor gets run over the jar without any actual process step. The work is essentially a no-op and it is creating a new jar that is the same as the old one. Basically, we are doing what amounts to an inefficient copy of the original jar.
With changes for bug 178884, there is also extra work that is being done when there is no nested jar and the processing didn't change the inf file.
JarProcessor is now in the provisioning world
fixed