Community
Participate
Working Groups
When a bundle specifies that it requires a specific execution environment (for example, J2SE-1.4), we should be able to verify that it only uses methods/types from that environment. In the IDE, a bundle might be compiled against a higher level EE and usage of a 1.5 JRE method would compile without errors, but cause a runtime problem.
Marking assigned for future consideration.
>we should be able to verify that it only uses methods/types from that >environment. ...and fields. Now, is there an official list of such elements? If not, how would this reliably be defined?
(In reply to comment #2) > Now, is there an official list of such elements? If not, how would this > reliably be defined? We would generate the list by comparing JDKs. We could do a binary compare, or use source code looking at @since tags.
Note that @since tags don't necessarily catch all visible changes, see e.g. last paragraph of http://java.sun.com/j2se/javadoc/writingdoccomments/index.html#@since > should be able to verify that it only uses methods/types/fields The unavailable members should no only not compile but already be filtered from content assist, organize imports, etc. Another caveat: If the bundle specifies multiple execution environments, we should only allow members that are available in all the EEs.
This has been addresssed, marking as dup of newer bug. We still have not addressed the code assist issue - I will open a new bug for that. *** This bug has been marked as a duplicate of bug 253693 ***
Opened new bug 256287 for code assist issue.
