[izpack-devel] System.out

[Jeff Gordon]

I hadn't used any of the logging facilities because of many other messages
stating how the logging was broken.  I've used Log4j for about 10 years now
and I think it has pretty much become the industry standard, but there are
many folks who prefer other things, and that's fine.  I would just like to
have a way to log the installation to a file.

- Jeff


On Jan 28, 2008 3:32 PM, Piotr Skowronek <piotr at skowro.net> wrote:

> Julien Ponge wrote:
> >> How about -DTRACE switch? It does the same as system.out.println. If
> >> something was wrong with the installer
> >> on client side, client can invoke the installer with this parameter to
> >> let logs to be printed on console.
> >> I guess this is much nicer than doing system.outs.
> >
> > Yep, this flag is also here for doing some logging.
>
> Maybe it would be nice to normalize the way
> the debug/info logging is done.
>
> We could use our logging class, that, in the future,
> would allow easy migration to other logging libs (for
> example log4java), just by alteration of this class.
>
> IzPack already has Debug.java, maybe everyone should
> use it to do some logging? Now, I can see lots of
> System.outs, I think these should go thru our logging
> class. This way we could control what should be displayed
> on console.
>
> Regards
> Piotr
> _______________________________________________
> izpack-devel mailing list
> izpack-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/izpack-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.berlios.de/pipermail/izpack-devel/attachments/20080128/81fc0756/attachment.html