• Post Reply Bookmark Topic Watch Topic
  • New Topic

JavaC error log  RSS feed

 
Keith Anderson
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi.
When I compile source and get errors, I would very mutch like these errors to be placed in an error log...
I would like to continue only using Notepade for development.
(The systems at my work are low on resources and it it technicaly .. against company policy to install a larger IDE)
I have tried "Javac bob.java > log.txt" and this doesn't work.
Our systems run Windows 98se.
I have used Textpad in the past and it serves my purposes very well. However it causes my system to lock up (slow down) periodicaly for 20-30 seconds at a time.
Any ideas?
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24217
38
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Keith,
Welcome to JavaRanch!
First of all, I'm very sorry to hear about your working environment. My condolences. Sounds awfully unpleasant.
Apparently, though, you're not the only person working under these conditions. here's a whole web page dedicated to precisely your complaint. Take heart!
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would like to continue only using Notepade for development.
(The systems at my work are low on resources and it it technicaly .. against company policy to install a larger IDE)

The company allows only Notepad for Java development? Just resign, man.
 
Adrian Yan
Ranch Hand
Posts: 688
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hhahahaha... that's mean dude...
Notepad should be the one beginners use anyway. Anyway, can you give us abit more information about sending to a log file?
 
Keith Anderson
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, My I am not a developer. I do Technical support on a 1-900 line. This is why our computes suck, all we do is Log our Calls on them. I am working on a 233mhz Packard Bell system. with 64mb memory. It is kinda fun figureing out ways to squeaze as mutch out of this system as possible ( Ok so I lied it SUCkS !!).
I appreciat all of your comments and your concerns.. lol.. (ok i am done crying now) THANKS
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to JavaRanch, Keith!
When I compile source and get errors, I would very mutch like these errors to be placed in an error log...
I have tried "Javac bob.java > log.txt" and this doesn't work.
Our systems run Windows 98se.

On Windows XP, "javac bob.java 2> log.txt" works.
On Windows XP, the > symbol is for normal console output, and 2> is for error output.
If that doesn't work, then from the javac documentation, I gather that the -Xstdout javac switch should redirect output to the System.out output stream, and so a statement such as "javac -Xstdout bob.java > log.txt" should do the trick, but it doesn't seem to work on my Windows XP machine.
You also might want to try "javac bob.java > log.txt 2>&1" which should direct both normal and error output to the log.txt file.
If you haven't tried it yet, you might want to try the search feature of our forums. (Note that the search page link is at the top right of this page.) I ran across one thread by Jon Dornback that is chalk full of advice on this topic.
Good luck.
[ October 12, 2003: Message edited by: Dirk Schreckmann ]
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!