Re: [pde-build-dev] JNLP, pack200, and nested jars

[Andrew Niefer <aniefer@xxxxxxxxxx>]

The pack.properties file also supports
a 'pack.excludes' property.  The value is a comma separated list of
jar names to exclude.

-Andrew

Thomas Hallgren <thomas@xxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

05/15/2007 05:39 AM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	[pde-build-dev] JNLP, pack200, and nested jars

I'm JNLP enabling an Eclipse based application. I'm
using Pack200 
(through the jarprocessor) to recude the bulk of the download. 
Everything is fine but one single thing. The 
'org.eclipse.core.resources_3.2.2.R32x_v20061218.jar' contains a nested
jar file. Apparently, this file is subject to a recursive pack200 and 
that is not understood by the JNLP protocol. From what I've understood,
it can do (and expect) recursive signing, but not recursive pack.

I've seen that the meta-inf/eclipse.inf file can be used to specify the
property jarprocessor.exclude.children.pack=true. I'm however, not the
owner of this bundle. I can patch it of course but I was wondering if 
there's some way I can specify this outside of the bundle. I know that
pack200 command line arguments can be passed using a '<jar>.pack.args'
property in a 'pack.properties' at the root of my zip file but that 
doesn't help me much.

Can I trigger the jarprocessor.exclude.children.pack in any other way 
then patching the actual eclipse.inf file inside of the bundle?

Thanks,
Thomas Hallgren

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev