Re: piece of $#!t eclipse can't find the main class
John Ersatznom 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)
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...
Yes, unfortunately that is what I'm claiming. I'm using Eclipse 3.1.2
(maybe a newer version fixes the problem). I decided to set an output
folder separate from my source files since I started using packages. I
thought it would make creating a JAR file easier since I wouldn't have
to worry about having source files mixed with the class files in the JAR
(although I think that can be avoided with specific syntax in making the
JAR).
I created an output folder and linked it to a real file system folder
which already had data in it. The folder that I linked to was called
"resources" and I created a new output folder in eclipse called
"production" and linked it to the "resources" folder. I expected a
folder called "production" to be created in "resources". What ended up
happening was that I compiled my project and got a complaint that a .bat
file that I had in the resources folder (and that was a resource in the
project) was missing. I went to the resources folder and none of the
files that used to be there were there any more and files from the
compilation process were there instead (like the .settings folder and
the .project file). Eclipse wiped out everything that was in the
"resources" folder without warning. It shouldn't need to do that (maybe
it does that automatically for cleaning purposes during a build but it
should warn you at the least). Needless to say, I was swearing up and
down for about half an hour after that.