[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Error Parser Improvements for 6.0 -- potential APIbreakage / addition
|
Although I do not work in this area +1 for me.
Randy
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of James Blackburn
Sent: Friday, May 29, 2009 3:31 PM
To: CDT General developers list.
Subject: [cdt-dev] Error Parser Improvements for 6.0 -- potential
APIbreakage / addition
Dear All,
We've been doing a fair bit of work (one might say too much!) on the
Error Parser Manager for 6.0 . It's now simpler, handles linked
resources better and is well documented!
Unfortunately it still doesn't handle EFS resources properly, and in
particular if a parsed path is ambiguous the Error marker is set on the
Project (as in CDT 5).
Bug 269023 : https://bugs.eclipse.org/bugs/show_bug.cgi?id=269023
aims to address this.
Unfortunately one of the patches is API breaking (in a very minor way):
URI getDefaultBuildDirLocationURI();
is added to org.eclipse.cdt.managedbuilder.buildmodel.IBuildDescription
in managedbuilder.core. This method complements the IPath method
#getDefaultBuildDirLocation().
In addition to this URI ErrorParserManager adds a URI constructor:
public ErrorParserManager(IProject project, URI
baseDirectoryURI, IMarkerGenerator markerGenerator, String[]
parsersIDs); And associated URI push / pop methods which mirror the
IPath based methods. Consumers can continue using Error Parser as they
did before, or use the new URI methods if they wish (relative IPaths are
made relative to the base URI of the current working directory).
What do people think about making this change in CDT 6? From a risk
perspective the changes made in EPM are API compatible, the change made
in managebuilder.core isn't, but is trivial to resolve...
Cheers,
James
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
