Re: piece of $#!t eclipse can't find the main class
Lew wrote:
Brandon McCombs wrote:
At one point tonight Eclipse was working fine. After specifying a
separate output folder for class files (and losing all the files in
that folder w/o Eclipse giving me a chance to do anything with them;
I hope i never meet any of the eclipse developers because they may
not live long if I do)
John Ersatznom wrote:
Are you claiming that setting a separate output folder of C:\foo in
Eclipse wipes out all preexisting files in C:\foo? That sounds like a
serious bug. Remind me never to do that myself...
Brandon McCombs wrote:
Yes, unfortunately that is what I'm claiming. I'm using Eclipse 3.1.2
(maybe a newer version fixes the problem).
So does Netbeans and most command-line Ant build files I've used.
The idea is that a build folder (e.g., where you build your .class
files) is a clean environment to contain your deployables and only your
deployables. A "clean" build perforce gets rid of all the files in the
output directory, which by assumption are *all* built from your input
files, so their loss should not be such a keen issue.
Well the files that were deleted were not output or input files. They
were configuration files I used to test the app.
Why in the world would you put files in the build folder that you wish
to keep?
Because I expected Eclipse to create the "production" folder that I had
specified in the Eclipse output folder dialog window. I thought it would
get created in the folder I linked it to instead of just replacing it.
At the least I think it should have warned me about deleting files,
especially ones that wouldn't result from the compilation process and
thus not normally be part of a cleanup process.
By the way, if this build folder is supposed to be where the
ready-to-deploy files are outputted, why is it that Eclipse puts the
project's .settings folder, the .classpath, and the .project file also
in the directory? Those don't need to be deployed so why should they be
in the folder?
Also, does the Run operation imply a Project->Build and a Project->Clean
operation or just a Project-Build? If the latter then I shouldn't have
lost my files since it did a Clean w/o telling me it would.
Don't go murdering Eclipse developers for doing the natural right thing
just because you didn't.
- Lew