398028 – [CBI] some jars not signed by CBI build (mostly source)

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

Bug 398028 - [CBI] some jars not signed by CBI build (mostly source)

Summary: [CBI] some jars not signed by CBI build (mostly source)

Status:	RESOLVED DUPLICATE of bug 396445

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Releng (show other bugs)
Version:	4.3
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Releng-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-01-12 17:54 EST by David Williams
Modified:	2013-04-29 22:59 EDT (History)
CC List:	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

2013-01-12 17:54:35 EST

In one of my first "test builds" on build.eclipse.org, using 4.2.2, since master is not building yet, I noticed that several bundles are not signed: 

The reason for org.aspectj.weaver could be lots of things ... but, guessing the source features are "pure CBI". 


   org.aspectj.weaver_1.6.7.20091231194938.jar:                                                                  jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.ant.core.source_3.2.401.v20121126-1856.jar:                                                       jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.pde.build.source_3.8.2.v20121114-1408.jar:                                                        jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.jdt.core.source_3.8.2.v20121122-1522.jar:                                                         jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.pde.core.source_3.8.1.v20121002-1550.jar:                                                         jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.core.resources.source_3.8.1.v20121114-1244.jar:                                                   jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.ant.ui.source_3.5.301.v20121210-2109.jar:                                                         jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.ant.launching.source_1.0.200.v20120523-1754.jar:                                                  jar is unsigned. (signatures missing or not parsable) 
   org.eclipse.help.base.source_3.6.101.v20121231-0737.jar:                                                      jar is unsigned. (signatures missing or not parsable)

Comment 1 Thanh Ha

2013-01-14 09:11:31 EST

We had an issue in Bug 396445 with regards to Tycho generated source bundles not being signed. However in this case it sounds like those ones are signed now and I guess these ones non-generated source bundles?

Comment 2 David Williams

2013-04-29 22:59:56 EDT

Counting as dup.

*** This bug has been marked as a duplicate of bug 396445 ***