 |  |  |  |  |  |  |  |
Want to remove debug information
 |
Hello everyone,
I am wondering how to remove debug information (for example, System.out or System.err) automatically when I build/compile a Java project? Does Java compiler or build tool has such options when we build/compile a Java application?
Thanks in advance,
George
I am wondering how to remove debug information (for example, System.out or System.err) automatically when I build/compile a Java project? Does Java compiler or build tool has such options when we build/compile a Java application?
Thanks in advance,
George
You can't, and you don't want to.
Once your application ships you want to be able to get some logs when there's a problem at a customer's site.
To get that build your application to log those messages to some file.
If you create a logger with different logging levels you can turn on different levels of logging at runtime by changing a config file or command line option.
Java has (from 1.4 onwards) a quite comprehensive logging framework built in, or you can use a 3rd party framework like Log4J.
Logfiles should at the minimum list a timestamp with every entry so you can trace what happened where, and best also a very good indication of where the entry was created (just using this.toString() is a good start, line numbers can help as well).
Once your application ships you want to be able to get some logs when there's a problem at a customer's site.
To get that build your application to log those messages to some file.
If you create a logger with different logging levels you can turn on different levels of logging at runtime by changing a config file or command line option.
Java has (from 1.4 onwards) a quite comprehensive logging framework built in, or you can use a 3rd party framework like Log4J.
Logfiles should at the minimum list a timestamp with every entry so you can trace what happened where, and best also a very good indication of where the entry was created (just using this.toString() is a good start, line numbers can help as well).
I had no clue you could do that in java. I looked at some of the logging api's, and it looked very useful.
Thanks all the same, server_crash. 
regards,
George
•
•
•
•
Originally Posted by server_crash
I don't recall anything like that. I would either leave them, or remove them manually.
regards,
George
Thanks jwenting,
Your reply is very helpful. I have learned so much dealing with log from you. Can you recommend some online resources to learn log related topics?
regards,
George
•
•
•
•
Originally Posted by jwenting
You can't, and you don't want to.
Once your application ships you want to be able to get some logs when there's a problem at a customer's site.
To get that build your application to log those messages to some file.
If you create a logger with different logging levels you can turn on different levels of logging at runtime by changing a config file or command line option.
Java has (from 1.4 onwards) a quite comprehensive logging framework built in, or you can use a 3rd party framework like Log4J.
Logfiles should at the minimum list a timestamp with every entry so you can trace what happened where, and best also a very good indication of where the entry was created (just using this.toString() is a good start, line numbers can help as well).
regards,
George
Thanks server_crash,
I am wondering how you debug your applications since you do not use log utility.
regards,
George
•
•
•
•
Originally Posted by server_crash
I had no clue you could do that in java. I looked at some of the logging api's, and it looked very useful.
regards,
George
Oh, there's System.out.println() which is what everyone used before dedicated loggers became available.
We created our own logging API, another favourite passtime in days past.
We created our own logging API, another favourite passtime in days past.
•
•
•
•
Originally Posted by George2
Thanks server_crash,
I am wondering how you debug your applications since you do not use log utility.
regards,
George
Thanks for providing information server_crash,
regards,
George
•
•
•
•
Originally Posted by server_crash
lol I never really did. Sometimes I used System.out.println()'s, and sometimes I just knew what to do from the error. I've never really created anything so big, that it require a lot of debugging. But, my text editor I'm working on right now is in need of it. So I might have to put it to some use.
regards,
George
|
Other Threads in the Java Forum
- Previous Thread: Looking for sound solution for J2ME.
- Next Thread: Help with a Calendar!!
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Java Posts
- Today's Posts
- Unanswered Threads
android api applet application apps array arrays automation awt bidirectional binary birt bluetooth businessintelligence busy_handler(null) card chat class classes client code collision columns component constructor database designadrawingapplicationusingjavajslider draw eclipse error errors eventlistener exception expand fractal game givemetehcodez graphics gui guidancer html ide image inetaddress input integer intellij j2me java javafx javamicroeditionuseofmotionsensor javaprojects jme jni jpanel jtree julia linux list loop machine map method methods mobile mobiledevelopmentcreatejar myaggfun netbeans newbie oracle physics plazmic print problem program programming project recursion scanner server set sharepoint smart sms smsspam sort sortedmaps sql string subclass support swing textfield threads tree trolltech unlimited utility webservices windows
