| Using Default Java Compiler to Build [message #291936] |
Tue, 27 September 2005 10:51  |
Eclipse User |
|
|
|
Originally posted by: Krishnan.Muthuswamy.gmail.com
Hi,
Even though I have set up default JDK to buid and compile Java Programs
(by going into Window -> Preferences -> Java -> Installed JRE, Eclipse
seems to be using its internal compiler to build. Is this true? The reason
why I am feeling this way is because, when I do remote debugging of my
J2EE application (built separately outside of Eclipse using Ant Scripts) I
can see the debugger jumping lines in the code while stepping through.
While most of the time this is not a big deal, the problem is when I have
the automatic build turned on, Eclipse and Ant Scripts sharing the classes
(bin folder) folder, creates ClassFormatError in the J2EE application.
This happens because Classes created by Eclipse are different from classes
generated by the default JRE Compiler which is used by my Ant Scripts.
Has anyone come across this issue?
Cheers
Krish
|
|
|
|
| Re: Using Default Java Compiler to Build [message #292203 is a reply to message #291936] |
Fri, 30 September 2005 12:26  |
| Eclipse User |
|
|
|
Originally posted by: automatic.javalobby.org
The debugger is unrelated to the compiler used to build the code. The compiled code (with debug information) reports when it goes past a different line, and Eclipse's debugger follows the cursor forward.
You are probably better off setting up Ant to use a different directory to the one that Eclipse uses for its compiled output. We've got a mechanism that does similar here, where we use Eclipse to do development work (and using an Eclipse-specific 'Build' folder) with an automated build (using a 'target' folder).
|
|
|
Powered by
FUDForum. Page generated in 0.03551 seconds
Home