Re: [p2-dev] How to tell that unpacked jar is good?

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

We don't know of any way, however running the tests on the normalized jars and also having those normalized jars be part of every download is what avoids you the bad surprise.
I think problems only occur if you leave pack200 as an after thought.


Henrich Kraemer ---04/09/2009 03:41:47 PM---Bug http://bugs.sun.com/view_bug.do?bug_id=6313847 'pack200/unpack200 creates corrupt class file' ap

From:	Henrich Kraemer <henrich.kraemer@xxxxxxxxxx>
To:	p2-dev@xxxxxxxxxxx
Date:	04/09/2009 03:41 PM
Subject:	[p2-dev] How to tell that unpacked jar is good?

---

Bug http://bugs.sun.com/view_bug.do?bug_id=6313847 'pack200/unpack200 creates corrupt class file' appears to be a case where unpack did not seem to fail, but problems at runtime occured.
The workaround seems to be to use effort 4 when creating the jar.

It appears that one cannot determine programmatically whether an unpacked jar is corrupt or is there a way? 

Thanks,

Henrich_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev