| Summary: | [JIT] Bundle have wrong EE | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Benjamin Muskalla <b.muskalla> |
| Component: | Incubator | Assignee: | Project Inbox <rap.incubator-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | austin.riddle |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Benjamin Muskalla
Ah, thanks...will address that. (In reply to comment #0) > The bundles currently have 1.4 as their Execution Environnment but use 1.5 > features. We should either correct the EE to be 1.5 if we need the Java 5 > features or downgrade the source to 1.4. Hey Benny, I can't seem to find any issues after changing my compiler compliance level to 1.4. Can you give me any explicit examples? Thanks. (In reply to comment #0) > The bundles currently have 1.4 as their Execution Environnment but use 1.5 > features. We should either correct the EE to be 1.5 if we need the Java 5 > features or downgrade the source to 1.4. You need an 1.4 JRE to see the issues as they are refer to classes that are not part of the 1.4 rt.jar Examples: StringBuilder cannot be resolved to a type Application.java /org.eclipse.rap.rwt.visualization.jit.demo/src/org/eclipse/rap/rwt/visualization/jit/demo line 188 The method nanoTime() is undefined for the type System Application.java /org.eclipse.rap.rwt.visualization.jit.demo/src/org/eclipse/rap/rwt/visualization/jit/demo line 192 ArrayBlockingQueue cannot be resolved to a type JITWidgetLCA.java /org.eclipse.rap.rwt.visualization.jit/src/org/eclipse/rap/rwt/visualization/jit/internal line 114 (In reply to comment #3) Thanks Benny, I just committed fixes for those. Are there any others? StringBuilder cannot be resolved to a type JITGraphLCA.java /org.eclipse.rap.rwt.visualization.jit/src/org/eclipse/rap/rwt/visualization/jit/internal line 49 StringBuilder cannot be resolved to a type JITGraphLCA.java /org.eclipse.rap.rwt.visualization.jit/src/org/eclipse/rap/rwt/visualization/jit/internal line 49 The method getCanonicalName() is undefined for the type Class JITWidgetLCA.java /org.eclipse.rap.rwt.visualization.jit/src/org/eclipse/rap/rwt/visualization/jit/internal line 49 The method valueOf(String) in the type Integer is not applicable for the arguments (int) TreeMapLCA.java /org.eclipse.rap.rwt.visualization.jit/src/org/eclipse/rap/rwt/visualization/jit/internal/treemapkit line 28 The method getCanonicalName() is undefined for the type Class ApplicationWorkbenchAdvisor.java /org.eclipse.rap.rwt.visualization.jit.demo/src/org/eclipse/rap/rwt/visualization/jit/demo line 37 I think you should be able to setup API Tooling to warn if you use classes that are not available in your EE. (In reply to comment #5) > I think you should be able to setup API Tooling to warn if you use classes that > are not available in your EE. Thanks Ben, I just checked-in what I think are all of the compliance changes, based on my new API tooling settings. ;-) Thanks for the tip! That was the first time I had ever used it. Austin, these issues seem to be resolved. Can this bug be closed? The correct project settings have been checked in. |