| Can Eclipse build to a location where there are existing .class files? [message #41747] |
Tue, 14 January 2003 16:59  |
 No real name
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
I am working on a subproject of a much larger project. The project delivers
files a "classes" directory, and it expects to see all classes there,
including mine.
So I changed my project's build path (in Eclipse) to point to this classes
directory. However the build then gave an error saying it could not clean
the output path. OK, it couldn't because it didn't know about all the
..class files and other packages already in the classes directory. I don't
know why it would want to clean all those, but it does!
So I went back to the project settings, Java Compiler, Other - then Use
Project Settings and deselect "Allow to clean output folders for a fully
build". (The wording's a big dodgy and this field isn't in the Help.)
Great! Now Eclipse gets much further. No cleaning to break! However,
because the .class files for my project are out there (not cleaned up), when
I do a Rebuild it gives an error for every file saying the .class file is
not written out! It can't compile a .java if the .class file is already out
there? And no, the .class file is not read-only.
So I delete all the .class files for my project. It still doesn't build! I
have to Refresh the project (I guess so it can spot all the .class files are
now gone) and the build works.
Yahoo! However, I don't want to have to clean all my .class files and
Refresh the project just to build. Is there a better way?
Could "Cleaning" the output folders just clean up .class files that will be
created by my project?
Or with cleaning off, could the compiler please overwrite an existing .class
file?
Cheers,
Graham Perks
graham_perks at my work, bmc.com
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03370 seconds
] 
Search
Help
Register
Login
Home
