Summary: | Implement JSR-201, part "static imports" | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | ilias <ilias> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://www.jcp.org/en/jsr/detail?id=201 | ||
Whiteboard: |
Description
ilias
2004-12-18 11:52:58 EST
Static import support was released weeks ago. "Static import support was released weeks ago." this information is false. JSR-201 part "static imports" is not yet fully implemented within JDT.Core. See the plan: " # Incremental Java Compiler [...] # static imports (jsr-201) (1 week) * coming soon : static method imports " source: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r3.1/main.html See the dependent bugs(just entered as dependend). This issue is valid, unique and open. [you should split the Bugzilla Component "Core" to Components "compiler, assist, model, search, formatter, DOM-AST] Do you even bother to look for duplicate PRs before you waste our time? *** This bug has been marked as a duplicate of 81706 *** There is a difference between a "duplicate" and ad "depends on" relation. reopened. - "Do you even bother to look for duplicate PRs before you waste our time?" yes, I do. There is no "duplicate" relation between the issues. But even if: Of course I cannot detect future entries [Bug 81706 was entered _after_ this here]. - can you please look more closer to the "depends on" entries, before you waste once more _my_ time [which I provide voluntarily, in contrast to your time, for which you are paid for by IBM (I assume)]. - Please do not close this Issue before "JSR-201, part, Static Imports" is implemented fully within JDT.Core, as defined by the "depends on" Issues. On Dec. 28th when you reopened this PR (I wish I could call it that, but there is no testcase showing a problem), there was a REAL PR. Please do not waste our time by reopening PRs without testcases that show the problem. *** This bug has been marked as a duplicate of 81706 *** See Comment 4, reopened. Changed Summary to describe a readable and more precise Issue. Added link to JSR-201 to the URL field. - "there is no testcase showing a problem" A testcase is not an requirement to file an issue. . reopened . |