Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geclipse-dev] Quality: stacktraces and println's removal

Hi all,

as this week is quality week prior to the 0.5 release, it would be the 
right time to finally remove all those printStackStrace()'s and println()'s 
which are listed here:
  
http://iwr-geclipse.fzk.de:8443/luntbuild/publish/gEclipse/NightlyBuild/geclipse-0.5_N20070923-0600/artifacts/Issues.html#prints
(or go to the daily build page and pick the last build, then "Issues.html")

I've removed a few of them by my own, but many more remain, for instance

	eu.geclipse.launch.glogin*  ->  13
	eu.geclipse.glite.info            ->  13
	eu.geclipse.jsdl*                  ->  11
	eu.geclipse.info                   ->  8
	eu.geclipse.gridbench         -> 4
and some few more with 1 or 2

Remember that there is the   LogExceptionSolution which is used 
automatically in the problem-dialogs, so the user can always log the 
exception if he wants if you throw a GridException, instead of using 
printStackTrace.
And logging output can be logged without bypassing eclipse with
Activator.logStatus( IStatus ) in many (or most?) plugins, which is nothing 
else als  getLog().log( IStatus ), and with that you can choose 
the "level".
Anyway, debugging output only useful for developers should be _avoided_ in 
a "real" release ;-)

Thanks, cheers, Ariel


Back to the top