Dive into Oracle ADF

Send me a mail
 Dive into Oracle ADF   Click to see the XML version of this web page.   (Updated: 2/3/2008; 9:18:15 PM.)
Tips and tricks from Steve Muench on Oracle ADF Framework and JDeveloper IDE

Search blog with Google:
 

Search BC4J JavaDoc:
 

October 2005
Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          
Sep   Nov

Get Firefox!

Tuesday, October 25, 2005

If you are like I am, then you rebuild your workspace or project in order to get a "big picture" view of all the problems left to fix. The list of all errors shows up in the JDeveloper Compiler log window, and you double-click on the first one in the list in order to go size-up the problem and fix it. Maybe it's just me, but at this point I re-build the current page or *.java source file that I've just fixed to make sure that my fixes have indeed solved the problem. At this point, you get the comforting message that the file has no compilation errors, however in JDeveloper 10.1.2 and versions before, recompiling one file would also blow-away the list of workspace/project-wide compilation errors. This was always maddening for me.

In JDeveloper 10.1.3, the team has implemented a new preference in the Tools | Preferences... dialog, on the Environment panel, called Clear Compiler Log Before Compiling. If you simply uncheck the checkbox for that preference, then recompiling a given file will prune its errors from the compilation log window (if you fixed the code, of course!) but it will leave all the other errors there for you to use like a Todo list of problems left to navigate to and fix.

This works in the 10.1.3 EA1 release, so you can try it out today.


1:55:39 PM    



© Copyright 2008 Steve Muench.