This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Javadoc of CompilerTask.isSuccessful() says it returns null even if the task is stopped. IMO it is not proper behavior. If a compiler task is just a part of an action (eg run execution profile) then the action is not able to detect if output of the compilation tak is ready for futher tasks (eg execution). I propose to return true just in case the compilation finished without any error.
The javadoc for org.netbeans.api.compilation.CompilerTask.isSuccessful returns true if no errors were encountered prior to compilation termination (invoking {@link #stop()} will return the compilation success for the portion of compilation completed). false will be returned if at least one error was reported during the compilation or the compilation terminated due to a compiler exception. Are you looking at the old compiler api's?
No, I was looking at the right API but type wrong return value (null instead of false) :-) For sure I will refine my proposal: Return true just in case the compilation finished without any error and any interruption (via stop()). Reasons remain same.
You are requesting that isSuccessful return false if the compilation was stopped correct? I am assuming the use case is that you don't want to execute something where the compilation was stopped prematurely.
Yes, exactly. Why is a compilation considered as successful even if it was interrupted? It does not make much sense to me.
committed
verified
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as CLOSED.