Summary: | JDK Compliance doesn't match javac generation from an IBM or SUN JDK | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | D Kelsey <dkel50> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 2.1 | ||
Target Milestone: | 2.1 RC3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
D Kelsey
2003-03-06 13:01:44 EST
This feels like the same problem as described in bug 33843. Did you notice the compliance setting in the Java compiler preference page (on classfile tab). It allows you to inform the compiler to mimic either jdk1.3 or jdk1.4 behavior (independantly from setting the target level). The behavior you expect is only available in 1.4 compliant mode (where you can toggle the target level to 1.1, and source level to 1.3). Is it ok to close ? *** This bug has been marked as a duplicate of 33843 *** From reporter: The description could match the problem, but I don't know for sure. I do know that on IBM and Sun javac compilers (jdk 1.3 and 1.4), compiling with a target of 1.2 or higher resolves the problem we see. However bug 33843 seems to not talk too much about the effects of target. Need to investigate a little more to determine if compliance level is enough to change behavior or simply the target level. Indeed -target has an side effect on the namelookup. To get this behavior in Eclipse, you need to change the compliance level. I tried to look for more documentation on this, but unsuccessfully. We know that -target changes the version numbers (major and minor). Would you have any pointer I could look at about the -target side-effects? Thanks. Released changes to look at targetJDK instead of complianceLevel to trigger this behavior. Olivier - please double check, and tag as fixed if verified ok. Actually, only tag as verified after verification. Verified. |