Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #21224
| From | Robert Klemme <shortcutter@googlemail.com> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Prevent Eclipse from IO access to source code on *any* GUI interaction |
| Date | 2013-01-08 23:30 +0100 |
| Message-ID | <al3l0qFiogfU1@mid.individual.net> (permalink) |
| References | <50eb3ae3$0$9515$9b4e6d93@newsspool1.arcor-online.net> |
On 07.01.2013 22:15, Marcel Müller wrote: > I am working with Eclipse Juno in a cross platform development. The > source code is on a NFS server, which is not that fast. NFS has also other issues (file locking, timestamps - might be dependent on the NFS version used) which make it a sub optimal choice for development and building in my experience. > Unfortunately Eclipse seems to access the source files over and over, I > guess to verify whether they are modified or removed in the file system. > This causes GUI interactions like moving files from one editor to > another to become incredibly slow. It sometimes takes seconds until the > green highlight responds to mouse movements. And often I create new > editors accidentally. Other actions like changing the current file are > affected too. > > Is it possible to avoid these kind of access? I do not need the up to > date checks. Especially not /that/ often. You can tweak that a bit via settings but I am afraid not to a level which would make working on an NFS share comfortable. > Using a local workspace speed up the things at least by a factor 10. But > this also increases the compile time on the remote machine by a factor > 10, which is definitely undesirable. That I don't really understand. Wouldn't you check out your files on the remote machine from some kind of version control system and build there? You're not placing only build artifacts on the NFS mount, do you? If you do not want to go down the route of distributed version control (which you should for a whole lot of other reasons) you could have your workspace local and rsync it when doing the build to the remote machine. Then start the build there. But this is really a crutch. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Prevent Eclipse from IO access to source code on *any* GUI interaction Marcel Müller <news.5.maazl@spamgourmet.org> - 2013-01-07 22:15 +0100
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Lew <lewbloch@gmail.com> - 2013-01-07 16:02 -0800
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Arne Vajhøj <arne@vajhoej.dk> - 2013-01-07 19:16 -0500
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Nigel Wade <nmw@ion.le.ac.uk> - 2013-01-08 09:37 +0000
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction "William Bonawentura" <nie@ma.mnie.pl> - 2013-01-08 15:03 +0100
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Arne Vajhøj <arne@vajhoej.dk> - 2013-01-08 19:55 -0500
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Robert Klemme <shortcutter@googlemail.com> - 2013-01-08 23:30 +0100
Re: Prevent Eclipse from IO access to source code on *any* GUI interaction Martin Gregorie <martin@address-in-sig.invalid> - 2013-01-08 22:56 +0000
csiph-web