Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #21205

Re: Prevent Eclipse from IO access to source code on *any* GUI interaction

From Nigel Wade <nmw@ion.le.ac.uk>
Newsgroups comp.lang.java.programmer
Subject Re: Prevent Eclipse from IO access to source code on *any* GUI interaction
Date 2013-01-08 09:37 +0000
Message-ID <al27ngF88b8U1@mid.individual.net> (permalink)
References <50eb3ae3$0$9515$9b4e6d93@newsspool1.arcor-online.net>

Show all headers | View raw


On 07/01/13 21:15, Marcel Müller wrote:
> Hi,
>
> I am working with Eclipse Juno in a cross platform development. The
> source code is on a NFS server, which is not that fast.
> 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.
>
> 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.
>
>
> Marcel

I fully understand the problem, it's just the same with NetBeans. I find 
it unworkable to have project source on an NFS server.

I would recommend that you install sub-version, or some other version 
control system on the NFS server. Choose one which is well supported in 
Eclipse. I don't use use Eclipes so can't recommend the best choice. I 
use the SVN plugin in NetBeans, which allows me to work from home just 
as easily as from my desktop at work.

Keep the repository on the central server. Check out a working copy 
which is then local to your IDE. Perform regular check-in/commit as 
appropriate. You can then build anywhere you wish, just check out/update 
the latest copy on the build system (or any other previous revision) and 
build it. You also get added the benefit of full revision control, which 
is something I'd recommend for anyone.

-- 
Nigel Wade

Back to comp.lang.java.programmer | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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