[izpack-devel] System.out
Julien Ponge
julien.ponge at gmail.com
Mon Jan 28 22:14:38 CET 2008
Hi Jeff,
> I noticed a recent commit was to remove a System.out and wanted to pose a
> question. How is console output and logging viewed by everyone? I added
> quite a few System.out statements to my code so I could run the installer
> via the command line and get the relevant console output to trace what was
> going on. I left many of the statements in just because I foresee having
> customers calling about issues which could be troubleshot much easier by
> having them run their install from the command line and sending in the
> console output. Without a fully integrated logging mechanism, this is
> really the only choice I have. I have a desire to attack logging here, but
> obviously there won't be anything substantial in the near term. So what are
> your thoughts? Running the installer as most users would hides all the
> console output and auto-installs aren't affected by it... Any objections to
> Log4j?
The System.out.println that I have removed was causing systematic
spurious "log [null]" messages to be displayed.
There have been a few discussions regarding logging in the past (you
can dig the archives to find it). Maybe others like Klaus and Elmar
can comment here.
Finally as far as log4j is concerned, I would prefer java.util.logging
since it is already bundled in the JDK API and does a very fine job
;-)
Cheers
More information about the izpack-devel
mailing list