Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 282318

Summary:	icu pack.gz file on RAP update site is invalid
Product:	[RT] RAP	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description David Williams

2009-07-02 15:41:52 EDT

While trying to understand some of the odd results in bug 282036 (where ICU doesn't get pulled into new repo) I discovered part of the reason is that the icu packed jar on the RAP site is not valid. 

This is the one in 
~/downloads/rt/rap/1.2/runtime-update/plugins 

com.ibm.icu.base_4.0.1.v20090415.jar.pack.gz:jarsigner: java.lang.SecurityException: SHA1 digest error for com/ibm/icu/text/BreakIterator$BreakIteratorHandle.class

Comment 1 Ralf Sternberg

2009-07-03 06:44:36 EDT

Hi David, I can reproduce this problem. All our pack200 file has been generated by the jarProcessor, and it seems that the icu.base is the only corrupt one.

Our first idea was to fix this by copying the icu.base pack200 file from the platform repository, but as also stated in bug 282036 comment #13, it turns out that there the icu pack200 files are empty. BTW, we've seen this error here too once. It seems that pack200 has some problems with icu.base.

I'd suggest just to leave the pack200 files out for icu.base and rebuild the metadata. The pack.gz saves 40kB, an amount that does not justify the trouble that it causes.
What do you think?

Comment 2 David Williams

2009-07-03 09:25:09 EDT

Yes, to leave them out is fine. But, do remember your meta data needs to be regenerated then. (the artifacts.xml/jar file). 

The platform's issue with icu*pack.gz. ia being tracked in bug 272140.

In general, the problem is this is a jar that we get "pre-built" so can not condition and pack it. 

My guess is you've have re-conditioned it.

Comment 3 Ralf Sternberg

2009-07-06 08:01:13 EDT

(In reply to comment #2)
> Yes, to leave them out is fine. But, do remember your meta data needs to be
> regenerated then. (the artifacts.xml/jar file).
Ok, I removed icu.base.pack.gz and re-generated the metadata.
The pack.gz for icu.base.source looks ok.
Changes are in the repository.

> In general, the problem is this is a jar that we get "pre-built" so can not
> condition and pack it.
> 
> My guess is you've have re-conditioned it.
Yes we did a normalize on all jars. But if I understand it correctly, the ICU jars should not be touched at all, right?

Comment 4 David Williams

2009-07-06 10:32:34 EDT

(In reply to comment #3)
> (In reply to comment #2)

> Yes we did a normalize on all jars. But if I understand it correctly, the ICU
> jars should not be touched at all, right?
> 

Correct.