Summary: | [1.5] NullPointerException during save and compile | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | jennifer.mendrys <jennifer.mendrys> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.1 M3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
jennifer.mendrys@embarcadero.com
2004-09-22 14:21:06 EDT
Please switch to use the latest 3.1 milestone, which contains our latest work on Java 5. We are also trying to use "cheetah" and it is my understanding that this will only work with 3.0. If I upgrade to 3.1 will I have to forego using cheetah? When is the eta on getting cheetah compliant with 3.1? Or is that necessary? The cheetah got integrated into Eclipse 3.1 deliveries. You no longer need the separate update, which isn't evolving anymore (as the cheetah now lives in 3.1 stream directly). Ok. Thanks. Another question. With 3.0 and cheetah, we were able to set our Compiler->Compliance and Classfiles to: compiler compliance level: 1.5 generated .class files compatability: 1.4 source compatability: 1.5 which allowed us to use the benefits of 1.5 for writing code, but generated our application at 1.4 levels. I am noticing that this is not the case in 3.1. If I set the compliance level to 1.5, I cannot set the .class file compatability to 1.4. Is this no longer an option? We were thinking that our app would ship about the time that 1.5 is officially released, and we didn't want to make our customers dependent on 1.5 installation. What would our options be? We never supported 1.5 source -> 1.4 target in our implementation. The preference page was simply broken, and allowed this mode to occur. This being said, were you able to deploy successfully 1.5 code on 1.4 target ? Lowering severity No more NPE in latest, but still issue with static generic method from raw type. Looks like static generic methods need to be treated differently from non-static generic ones on raw types. Tuned implementation, added regression test: GenericTypeTest#test336 Note: if #myMethod was made non-static, it would issue a compile error. Fixed Verified for 3.1M3 with build I200411040100 |