Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335950 - No "The JRE container on the classpath is not a perfect match..." when it should be reported
Summary: No "The JRE container on the classpath is not a perfect match..." when it sho...
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 06:44 EST by Szymon Brandys CLA
Modified: 2011-02-07 16:13 EST (History)
3 users (show)

See Also:

Attachments
My workspace (8.04 MB, application/zip)
2011-02-01 07:36 EST, Szymon Brandys CLA 		no flags Details
View All 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 Szymon Brandys CLA 2011-02-01 06:44:47 EST 
3.7 M5, IBM vm 1.6.0 and 1.4.2

Steps:
1) Unzip the attached workspace
2) Open M5 using the workspace 
3) There should be "The JRE container on the classpath is not a perfect match to the 'J2SE-1.4' execution environment" error or warning. But I can't see it on my fresh M5 installation.

The workspace was created using some of older integration builds updated to M5 using the p2 update site.
Comment 1 Dani Megert CLA 2011-02-01 06:57:49 EST 
Simple Steps:
1. start a new workspace with 1.6 JRE
2. import 'org.eclipse.text' either as source or from repository
3. change 'Java Build Path' to use workspace default JRE
==> GOOD:
The JRE container on the classpath is not a perfect match to the 'J2SE-1.4' 
is reported on MANIFEST.MF.

4. go to 'Installed JREs' preference page and add a 1.4 JRE, but don't choose
   it to be the default
==> GOOD: project is still using 1.6
5. clean the project (and let it rebuild)
==> BUG: warning on MANIFEST.MF is gone but should still be there because the JRE on the classpath is not a perfect match.
Comment 2 Szymon Brandys CLA 2011-02-01 07:15:07 EST 
I was not able to upload my zipped workspace, but Dani's steps will help to reproduce the issue.
Comment 3 Dani Megert CLA 2011-02-01 07:17:21 EST 
(In reply to comment #2)
> I was not able to upload my zipped workspace
Did you check the 'Big File' option?
Comment 4 Szymon Brandys CLA 2011-02-01 07:36:00 EST 
Created attachment 188037 [details]
My workspace
Comment 5 Szymon Brandys CLA 2011-02-01 07:38:49 EST 
(In reply to comment #3)
> (In reply to comment #2)
> > I was not able to upload my zipped workspace
> Did you check the 'Big File' option?

The 'Big File' option is not available in Mylyn editor :|
Comment 6 Dani Megert CLA 2011-02-02 11:51:00 EST 
This is a regression which got introduced during 3.6.
Comment 7 Dani Megert CLA 2011-02-03 08:51:10 EST 
(In reply to comment #6)
> This is a regression which got introduced during 3.6.

This is caused by bad fix for bug 307247.
Comment 8 Dani Megert CLA 2011-02-03 09:07:01 EST 
Fixed in HEAD (BundleErrorReporter.java, rev. 1.75).
Available in builds >= N20110203-2000.

Curtis, please verify the fix.
Comment 9 Curtis Windatt CLA 2011-02-07 16:13:34 EST 
Verified