Summary: | CategorizedProblem's category should be available from markers | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 3.2 | ||
Target Milestone: | 3.2 M5 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: | |||
Bug Depends on: | 119444 | ||
Bug Blocks: |
Description
Markus Keller
2005-12-06 12:39:54 EST
I did not add the #category API from marker, until we know what is needed to meet requirements. Note that the category can always be determined from the ID, so I would favor a static method on CategorizedProblem#computeCategoryID(int problemID) Would this do the trick ? If a static alternative is preferred, then it would result in an extra slot into the problem marker itself, which is likely fine anyhow. Which way do you prefer ? Hm, could you add CategorizedProblem#computeCategoryID(int problemID) for now with the risk of having to add the category attribute later? This would allow us to play with the current problems view implementation. The final decision will have to wait for bug 119444. Java problem markers now have an attribute "categoryId" so as to persist the category they belong to. Marking as FIXED (it was actually released into v_635). Verified |