Mod "debug"

[GoogleCodeExporter]

Another improvement that can be nice I think: an optionnal "debug" mod. 

Like all the trace printed (except errors) are not necessary useful and if you 
use it on a big collection and want to see if there are problems it produces a 
lot of text.

So it could be a field in the config.properties to activate or not this option.

But need to change everywhere in the code where there is a print to show what 
is done and add someting like that:
if(Config.get(Config.DEBUG).equals("true")) {
System.out.println("trace");
}

Original issue reported on code.google.com by damien.p...@gmail.com on 25 May 2012 at 8:02

[GoogleCodeExporter]

Hey again,

just to be sure we're on the same side: would a new command line switch for the 
standalone version that enables debug output be sufficient? Because the output 
code is largely already present, just not enabled in the productive versions, 
and it does produce a lot of output.

Original comment by jul...@gmail.com on 26 May 2012 at 9:18

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I find that in the standalone version it produces too much already ;)

Original comment by damien.p...@gmail.com on 26 May 2012 at 7:49

[GoogleCodeExporter]

oh, so you want it LESS verbose?

Original comment by jul...@gmail.com on 26 May 2012 at 8:01

[GoogleCodeExporter]

yes! if you run it on big collection you don't want to see each step it pass 
by, only errors that happens

so it could be nice if in the future "trace" become something you can choose or 
not

Original comment by damien.p...@gmail.com on 26 May 2012 at 8:24

[GoogleCodeExporter]

I guess that sounds reasonable. Will look into it once the time to do so 
presents itself.

Original comment by jul...@gmail.com on 29 May 2012 at 9:50

• Changed state: Accepted

[GoogleCodeExporter]

finally got around to implementing this in r04ea9c3368aa.

what i've done is change the default behavior to being quiet; i.e. only the 
desired tagged output text is printed.

verbosity can be enabled using two new command line switches: -v for verbose 
(INFO-level) and -vv for very verbose (ALL).

damien,
in case you want to try it out, i'm attaching a .jar file that reflects the 
current development status. you should be able to use it as a drop-in 
replacement for the current stable version. if you happen to find any 
undesirable behavior, please let us know here.

Original comment by jul...@gmail.com on 26 Jun 2012 at 1:13

• Changed state: Fixed

Attachments:

• de.unihd.dbs.heideltime.standalone.jar

[GoogleCodeExporter]

I tried, it works good!
Thanks for the enhancement

Original comment by damien.p...@gmail.com on 27 Jun 2012 at 1:43

[GoogleCodeExporter]

thanks for the feedback! i've played around with it, it seems to work just as 
expected.  setting this to verified.

Original comment by jul...@gmail.com on 27 Jun 2012 at 3:14

• Changed state: Verified

[GoogleCodeExporter]

Original comment by j.z...@stud.uni-heidelberg.de on 18 Apr 2013 at 10:11

• Changed state: Deployed