Summary: | Builder participants should create their own marker types | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.2 | ||
Target Milestone: | 3.2 M6 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Philipe Mulet
2006-02-16 10:37:32 EST
Also, the format of the marker generated is reusing the Java problem template, i.e. clients cannot add more attributes if they want. CategorizedProblem defines some minimal contract, and certainly current attributes are ok, but clients should be allowed to create more. For M5, ensured that API side is in place. Implementation will honour these during M6. * Added API CategorizedProblem#getExtraMarkerAttributeNames() and getExtraMarkerAttributeValues() to allow to specify extra attributes in problem markers. * Added 'managedMarker' sequence on 'compilationParticipant' extension point to declare marker types that are persisted by the Java builder. Changed JavaModelManager.CompilationParticipants to take the 'managedMarker' sequence into account. Also changed AbstractImageBuilder to create markers only if the corresponding categorized problem has a managed marker type. Finally changed JavaBuilder to delete all managed markers for a given resource. Updated APT plugin.xml and APT tests to reflect this change. Verified for 3.2M6 using build I20060327-0010. |