The update client looks for the unpack200
executable in a number of places (including in the JRE, on the path and
in a special var). If it is available, Update and hte update site
being used supports pack200 content, the client will attempt to fetch .pack.gz
files. This way people running 1.4 (whatever) are still able to take
advantage of the new technology.
I updated the Update Site Optmization
wiki page with some info on this. No doubt Andrew will have something
Doug Schaefer <DSchaefer@xxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
04/24/2006 09:18 PM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew
Sent: Monday, April 24, 2006 5:27 PM
Subject: [cross-project-issues-dev] Update Site improvements for Callisto
Starting in RC2 (or nightly build N20060423-0010) org.eclipse.update.core
will have support for optimizing update sites. This support takes
the form of digests and Pack200.
Pack200 is a jar compression utility in J2SE 5.0, using it can reduce the
size of a jar by about 60% depending on its contents. However, Pack200
makes non-semantic changes to the class files. To ensure that the
bits downloaded from a packed update site are the same bits the you get
from a normal zip distribution, project should condition their jars as
part of their build process.
I have put together 2 wiki pages to cover this issue: http://wiki.eclipse.org/index.php/Update_Site_Optimization
Projects should please take a look and send me any feedback or questions
you may have.
cross-project-issues-dev mailing list