Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315025 - invalid packed.gz file for org.eclipse.jst.jsf.facelet.core
Summary: invalid packed.gz file for org.eclipse.jst.jsf.facelet.core
Status: RESOLVED WORKSFORME
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: 3.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: webtools.releng CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 01:40 EDT by David Williams CLA
Modified: 2018-06-29 15:14 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2010-05-31 01:40:59 EDT 
The following error occured when building Helios:

org.eclipse.core.runtime.CoreException: Unable to unpack artifact osgi.bundle,org.eclipse.jst.jsf.facelet.core,1.0.0.v20100526 in repository file:/shared/helios/aggregation/final/aggregate: Invalid content:org/eclipse/jst/jsf/facelet/core/internal/registry/taglib/faceletTaglib/util/FaceletTaglibValidator.class
Caused by: org.eclipse.osgi.signedcontent.InvalidContentException: The file "org/eclipse/jst/jsf/facelet/core/internal/registry/taglib/faceletTaglib/util/FaceletTaglibValidator.class" in the jar "/tmp/signatureFile10448.jar" has been tampered!
Comment 1 David Williams CLA 2010-05-31 02:06:59 EDT 
I'm not sure that could have led to this valid pack.gz file. For now, for RC3 Helios, I've removed the pack.gz version from our repo, so the common repo build will just get the jar. 

May be trouble with signing? 

Raghu, for now there's nothing for you to do here. As we produce new builds, we should "watch" each one more closely, make sure everything gets signed properly, and packed properly.
Comment 2 David Williams CLA 2010-05-31 03:13:28 EDT 
jar seemed signed correctly. We'll check next build (or, next time I "pack" which is currently a "manual" step ... normally not done until the last minute, but should do more frequently to check this problem. If the problem re-appears, we'll probably just mark that jar not to be packed, for a quick fix.
Comment 3 David Williams CLA 2010-06-18 22:43:46 EDT 
seems fine. Some quirk, I guess?