[Clirr-devel] [ clirr-Feature Requests-1710276 ] Don't let exceptions kill the build

[SourceForge.net <no...@so...>]

Feature Requests item #1710276, was opened at 2007-04-30 22:57
Message generated for change (Comment added) made by lkuehne
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1710276&group_id=89627

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface Improvements (example)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nascif Abousalh Neto (nascif)
Assigned to: Nobody/Anonymous (nobody)
Summary: Don't let exceptions kill the build

Initial Comment:
When using Clirr to create reports, failures related to the class loading (missing jars or classes) would be better reported with the remaining errors to stdout or the output file - perhaps a special category called "FAILURE" could be created to support those.

The fact that those errors kill the Clirr process and dump a stack trace to stderr makes them it hard to integrate Clirr with other tools through automated scripts to generate reports. 

Thanks,
  Nascif



----------------------------------------------------------------------

>Comment By: Lars Kühne (lkuehne)
Date: 2007-05-01 13:58

Message:
Logged In: YES 
user_id=401384
Originator: NO

I didn't find any calls to System.exit() in the core checker code.
Which frontend are you using (Commandline/Ant/Maven) and what do you mean
by "kill the Clirr process"?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1710276&group_id=89627