Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
Fun with Eclipse
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Roedy Green, post: 616657"] I have had some more experience with the beast and I wish I had read the following few paragraphs before I started. I got is so much trouble trying to modify Eclipse *.java files behind its back. My changes kept disappearing. Eclipse is a true SCID. You may have no interest in how Eclipse works under the hood, but you had better understand at least as much as I am about to explain. This means its stores your Java source code in a structured database. This is how it can navigate so quickly, do global renames, refactor, find references and declarations instantly, compile instantly and undo changes, etc. It does not use Javac.exe at all (except in an ant build). It tokenises your source as you type and uses its own incremental/background compiler when you hit save. Every time you click save at saves a conventional *.java copy of the class source on disk along with a corresponding compiled *.class file. However, if you modify one of those files, delete it, rename etc., nothing happens. It is as if Eclipse were oblivious to your changes. The true copy of your program is inside the database. To allow other programs to change your source code, don't touch Eclipse's *.java files. They there mainly for curiosity, for backup and for CVS. In the case the entire Eclipse database were corrupted, you would lose nothing since your last save, even if you had no backup of the eclipse database itself. Instead of meddling with Eclipse's *.java files, export, fix with your conventional tools and editors and the import the back again. Import is the trickiest feature of Eclipse. Check after every import that your new source overrode the old and went into the correct place. It is so easy to mess up and effectively lose all the work you did outside Eclipse. If you screw up, you can compare Eclipse files with your exported ones, correct your copy of the files with Diffzilla, and reimport them. Again, there is no point in using Diffzilla to directly fix the Eclipse files. -- Bush crime family lost/embezzled $3 trillion from Pentagon. Complicit Bush-friendly media keeps mum. Rumsfeld confesses on video. [URL]http://www.infowars.com/articles/us/mckinney_grills_rumsfeld.htm[/URL] Canadian Mind Products, Roedy Green. See [URL]http://mindprod.com/iraq.html[/URL] photos of Bush's war crimes [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
Fun with Eclipse
Top