[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Exposing headless build results
|
We just checking problem markers
protected boolean isBuildOK() throws CoreException {
IMarker[] errorMarkers = fProject.findMarkers(
ICModelMarker.C_MODEL_PROBLEM_MARKER, true, IResource.DEPTH_INFINITE);
if(null != errorMarkers) {
for(int i = 0; i < errorMarkers.length; ++i) {
Object o = errorMarkers[i].getAttribute(IMarker.SEVERITY);
if(o instanceof Integer) {
if(((Integer)o).intValue() == IMarker.SEVERITY_ERROR)
return false;
}
}
}
return true; // Cannot detect; assume OK
}
2010/5/6 Dmitry Kozlov <ddk@xxxxxxxxxxxxxxxx>:
> I'm working on issue *300554*
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=300554> CDT headless build
> extension to report build success/failure by headless build application exit
> code.
> But I faced that IProject doesn't return exit code, and in
> Project.internalBuild() result, returned by BuildManager
> result = workspace.getBuildManager().build(...)
> is not exposed.
>
> Moreover, in BuildManager.basicBuild() this result is always setup with code
> indicating that there was a build error:
> MultiStatus status = new MultiStatus(ResourcesPlugin.PI_RESOURCES,
> IResourceStatus.INTERNAL_ERROR, Messages.events_errors, null);
>
> Is it possible (and what's the procedure is) to change platform API to add
> build which returns build result?
>
> May be you guys can suggest other ways to workaround this platform API
> limitation to return build result?
>
> Dmitry
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
