The Jar Processor will recurse and pack
nested jars while the pack200.exe doesn't. This is the likely explanation
for the size difference you are seeing.
So whether or not unpack200 would work
on a pack.gz file made with the jar processor would depend on whether or
not there were nested jars.
The Jar processor does provide a Main
class so that it can be used without having the eclipse executable. In
fact you can export the jar processor as a stand-alone jar separate from
update by using org.eclipse.update.core/org.eclipse.update.internal.jarprocessor/jarprocessor.jardesc.
pde-build-dev-bounces@xxxxxxxxxxx wrote on 06/06/2006
> Hi, > I have read the information I could find on Jar
> Pack200 including: http://wiki.eclipse.org/index.php/Pack200 > I used Jar Processor to pack the plugins directory
of my RCP. The
> Jar Processor reduces the size from 41MB (zipped) to 9MB. This
> awesome. However, if I just use pack200.exe with -G it is 25MB,
> it seems that Jar Processor is doing something else as well. I
> see looking at the contents of the directory that this is so. > It is not clear to me from the documentation
if Jar Optimizer is
> intended to be used for RCP, or just for Update sites. I am
> unclear as to whether I can unpack the files packed with unpack200.
> exe or if I need to have an Eclipse executable on the client
> machine. If it is the later then this won't work for an RCP. > Susan Foster
> Intel Corporation _______________________________________________
> pde-build-dev mailing list