Eclipse woes

We're using Eclipse 3.0 on my current project and while it has some nice features, I seem to be running into workspace problems every couple of days. For example, Eclipse will be working fine and then start complaining about files that can't be found. At this time, I usually refresh the source tree(s), clean the workspace, build and sometimes even close Eclipse. After a few cycles of this, Eclipse will finally sort itself out. I do quite like the incremental build feature, but it does throw up some weird errors from time to time.

The other thing that's recently happened is that (my copy of) Eclipse doesn't seem to know about some of our classes anymore. Ctrl-Shift-T lets you find a type quickly and I use this all the time to find classes within the project. As an aside, you can do this in IntelliJ with Apple-N (on Mac). Anyway, the list of our classes Eclipse knows about is getting shorter and shorter by the day! Something is certainly wrong with my workspace. Does anybody else have similar problems, or does Eclipse just know that I'm an IntelliJ user?

Tags : java

Responses[7]

Posted by Simon Brown on 18 January 2005 21:49:43 GMT #

Re: Eclipse woes

Comment from Jon Eaves on 18 January 2005 22:28:43 GMT #

Eclipse likes to be the centre of the universe. If you do stuff outside of Eclipse (like directly editing files) compilation, moving stuff around, CVS then it get's all hissy. <p/> Liking Eclipse (or not) is about accepting it's model on development. I've used Eclipse and IDEA (but mostly Eclipse) and watching people use both can be quite different. <p/> The "find type" behaviour you're seeing is super-weird and I've not seen that (having used nearly every Milestone of Eclipse since 2.1) however if you're building or changing libraries outside of Eclipse's knowledge, then that might cause it. <p/> Eclipse is user friendly, it's just very picky about it's friends ;-) <p/> (Stolen from an old Unix quote)

Re: Eclipse woes

Comment from Simon brown on 18 January 2005 22:40:45 GMT #

I've used WSAD 5.x in the past and that gets even more hissy if you start changing stuff (e.g. J2EE config files) underneath its feet! I think my plan of action is to try a different workspace. I am so glad that Eclipse starts up quick on my dual P4 box! ;-)

Re: Eclipse woes

Comment from Jon Eaves on 18 January 2005 22:43:50 GMT #

Don't get me started on WSAD. That's just plain evil.

Re: Eclipse woes

Comment from Dan Campers on 19 January 2005 01:13:00 GMT #

If it goes funny again, try adding the -clean argument to eclipse when you startup. Pretty sure this clears out the metadata, so hopefully gets rid of what causing the problems

Re: Eclipse woes

Comment from Simon Brown on 19 January 2005 08:57:18 GMT #

Thanks, I'll give that a go.

Re: Eclipse woes

Comment from Geoffrey Wiseman on 19 January 2005 18:04:08 GMT #

If you haven't done so already, you might want to turn on the preferences option that has Eclipse automatically refresh the workspace. Depending on the kind of problems you're seeing, that might help.

Re: Eclipse woes

Comment from michael on 23 January 2005 05:01:39 GMT #

One thing you should do -- is not to worry about changing things outside of Eclipse if that's the way you like to work. However, if you do work like that, then whenever you go back to Eclipse, right click on the project and then select the 'refresh' option from the popup menu. That should fix all that ails you.

Add a comment Send a TrackBack

Re: Eclipse woes Comment from Anonymous on 22 November 2008 06:16:12 GMT #
Title
Body	HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me	Yes No
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).