Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316137 - org.junit4_4.8.1.v20100525 bundle in test framework not signed
Summary: org.junit4_4.8.1.v20100525 bundle in test framework not signed
Status: CLOSED DUPLICATE of bug 256509
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 10:14 EDT by Ben Vitale CLA
Modified: 2010-06-08 11:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Vitale CLA 2010-06-08 10:14:19 EDT
Build Identifier: S-3.6RC3-201005271700

I noticed the copy of org.junit4_4.8.1.v20100525 included with the Eclipse Test Framework does not have any signer info. The copy included with the platform does have signer info.

I noticed this when I overlaid ETF on top of base Eclipse. Since there is some overlap, I blindly accepted the overwrite prompts, assuming any content shipping with ETF would match that which ships with the platform. Overwriting replaced the MANIFEST with the unsigned version, but left the other META-INF/eclipse.* files in place.

p2 noticed this when I was trying to install a feature using the director and the feature contained said bundle. It said the bundle had been tampered with, which it appears is accurate.

The workaround is easy: I just won't replace any files from that particular bundle when I extract the ETF.. but it sorta caught me off guard.

Reproducible: Always

Steps to Reproduce:
1. Unzip the base 3.6 platform
2. Unzip the ETF over top of it
3. Build a feature including the ETF
4. Attempt to install the feature into a product
Comment 1 John Arthorne CLA 2010-06-08 10:32:13 EDT

*** This bug has been marked as a duplicate of bug 256509 ***
Comment 2 Kim Moir CLA 2010-06-08 10:45:40 EDT
Okay, it's not recommended that you unzip stuff over your SDK.  It's preferable that you install it using the Help->Install new software.  

That being said,there is an enhancement request to change the test framework to a repository that can be installed.  See bug 310267.  

In the interim, you can copy the test framework to the dropins folder.
Comment 3 Ben Vitale CLA 2010-06-08 11:12:08 EDT
(In reply to comment #2)
> Okay, it's not recommended that you unzip stuff over your SDK.  It's preferable
> that you install it using the Help->Install new software.  
> 
> That being said,there is an enhancement request to change the test framework to
> a repository that can be installed.  See bug 310267.  
> 

Thanks for the pointer to that bug.

Just been lazy on moving away from unzipping for setting up base Eclipse in a build environment. Caught me on that one.

I started down the proper road but was a bit overwhelmed with the steps for setting up the delta pack (http://aniefer.blogspot.com/2009/06/using-deltapack-in-eclipse-35.html?showComment=1254488125896#c2983603127034020444)

I'll go back and have a second look. Cheers!