In article <4ad37d4a$0$289$14726298@news.sunsite.dk>,
=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk> wrote:
Lew wrote:
Arved Sandstrom wrote:
NOTE:
can't remember about NetBeans, but if you make changes to project
files
outside Eclipse, don't forget to refresh once you're back in the IDE.
That is an aspect of Eclipse that I find annoying. It has this
mysterious shadow copy of files that don't necessarily match what's on
disk even when you don't have editing changes pending. NetBeans
appears to work directly from the file system, which I prefer.
My guess is that the apps you write are also caching data.
Eclipse is using the equivalent of commit option A.
Yeah, but Eclipse sits there and says "My file copy is out of date. You
aren't going to be able to see jack shit unless you refresh. In fact,
I'm not even going to show you my old copy. It's old and nasty and you
wouldn't like it. Please hit F5 to refresh (unless you are in a mode
where F5 won't refresh, in which case hit something else)".
Why it can do this and not refresh for me is... puzzling. Maybe it's
just lonely and likes talking to someone.
But I am not so surprised. We are not supposed to edit files
behind Eclipse's back. If Eclipse detects it then it wants us