[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 21:01

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

Well, the core engine can't do anything useful when jars or classes are
missing, so I think it's OK to bail out with an exception. In Checkstyle
(where I'm also a committer) we report setup problems along with all the
code problems we find, and this causes an endless stream of support
requests. I'd like to avoid that mistake in Clirr.

If you look at the code for the clirr command line frontend in
net.sf.clirr.cli, you'll find that it catches some expected exceptions and
sets the exit code only in the main method. I should add a catch block for
RuntimeException, that is currently missing, and that is why you see stack
traces. Good catch :-)


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

Comment By: Nascif Abousalh Neto (nascif)
Date: 2007-05-01 15:10

Message:
Logged In: YES 
user_id=263845
Originator: YES

I am using the command-line - have not tried the others.

By killing the process I mean not handling runtime errors when running
clirr, and calling System.exit. This is not so bad for me now because I am
calling Clirr multiple times, one for each jar, since I want to be able to
group the generated messages. 

But the output to stderr and the stack traces for uncaught exceptions are
problematic. 


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

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