Bug 150343 - hardcoded jre names and sharing projects
Summary: hardcoded jre names and sharing projects
Status: RESOLVED DUPLICATE of bug 191804
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core
Depends on:
Blocks: 150336
  Show dependency tree
 
Reported: 2006-07-12 00:39 EDT by Grahame Grieve CLA
Modified: 2007-06-22 10:23 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grahame Grieve CLA 2006-07-12 00:39:47 EDT
My default jre for eclipse and projects is jre1.5.0_06. For a particular project, I am asked to ensure that it works on java 1.4. It's not enough to set the compiler to 1.4 compliance, I must also not use classes and features that were introduced in Java 5. According to the information in bug 40098:

> It is far simply for you to manually to simply switch your JRE setting
> for the project match your expectation (see installed JREs preferences,
> and add the ones you care about)

This works fine, but isn't practical when sharing projects between developers - because it's done by jre name, and our jre names may not match. So then they report bugs because the build path doesn't work, and we argue about jre sub versions. Can we have a solution to this problem? 

it seems most appropriate to add a new feature allowing jre's to be associated with the compiler compliance level, so that we can say, this project has compliance for 1.4 and also uses the 1.4 jre - whichever one of them you have chosen or are required to use.
Comment 1 Jerome Lanneluc CLA 2007-06-22 10:23:26 EDT
Moving to JDT UI
Comment 2 Jerome Lanneluc CLA 2007-06-22 10:23:48 EDT

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