Eclipse clean output folder when change file

I have a remote debugging. (The server is JBoss). It use to work ok, but now when i change a file (just add sysout) during debug i see in "work progress" that eclipse build a lot of files that not relevant for this class, eclipse also clean output folders and copy resource all as a result of just adding system.out.

I don�t know what has been changed. i remove eclipse and workspace, but didn�t help (the same preference). It took too much time and also in remote debug it cause to get unsynchronized message.

Cleaning output folders when you do a build is a project option that's turned on by default. To change it, open the project Preferences dialog and select Java Compiler/Building - it's under the Output Folder options.

The reason for this is that Eclipse is attempting to guarantee that the source code in your project is, in fact, sufficient to create the desired output and that any obsolete output be removed from the system. Sometimes "obsolete" output really wasn't obsolete, and even if it was, it's wasting space.

This is one reason why when I work with code generators I prefer to use 2 source directories. One for static code and one for generated code. Your life will be much more pleasant if directories are input-only or output-only and don't attempt to be both. Generated code is both at some time in its life, but by isolating it, you can nuke and re-generate without harming the static source.

An IDE is no substitute for an Intelligent Developer.

avihai marchiano
Ranch Hand

Joined: Jan 10, 2007
Posts: 342

posted May 22, 2008 07:36:00

0

The option that i have there is - "scrub output folders when cleaning projects".

This is not the case and also i don�t generate sources.

The case is: Startup JBoss server Connect with remote debug. Change one line in class (add space to string) and save. in the work progress i see that eclipse build workspace and compile a lot of irrelevant projects and also clean some output folders.

This waste time and also popup message on unsynchronized (but the debug still work in most cases).