| setting up a huge source directory [message #99032] |
Thu, 01 September 2005 20:50  |
Eclipse User |
|
|
|
Originally posted by: veniamin.nortelnetworks.com
We are using ClearCase for source control. Under Windows (the platform I
am having problems with) it appears as a mapped drive. The files are
currently organized in such a way that the root of the java source files
(the 'com' directory) is at the same "base" directory as all the other
files (such as C and C++ apps and libraries, configuration files and so
on). When I set up an Eclipse project, I set the "base" directory as the
source folder in the Java Build Path dialog. The problem is that Eclipse
automatically tries to discover and refresh the entire contents of the
"base" directory(which takes a VERY long time), whereas I am only
interested in the contents of the 'com' directory.
Evidently, defining filters on a source directory (Included and Excluded
patterns) only affects what is shown in the Package Explorer AFTER
everything is discovered, and not what is discovered and refreshed. Is
there any way to configure Eclipse to only look at contents of the 'com'
directory and ignore everything else under the "base"?
I am trying to avoid having to modify the current ClearCase directory
structure so to put the 'com' directory under another dedicated directory
to narrow down the 'java source context'.
Any insight will be very helpfull
|
|
|
|
| Re: setting up a huge source directory [message #99811 is a reply to message #99032] |
Tue, 06 September 2005 12:05  |
| Eclipse User |
|
|
|
Originally posted by: eclipse3.rizzoweb.com
veni wrote:
> We are using ClearCase for source control. Under Windows (the platform I
> am having problems with) it appears as a mapped drive. The files are
> currently organized in such a way that the root of the java source files
> (the 'com' directory) is at the same "base" directory as all the other
> files (such as C and C++ apps and libraries, configuration files and so
> on). When I set up an Eclipse project, I set the "base" directory as the
> source folder in the Java Build Path dialog. The problem is that Eclipse
> automatically tries to discover and refresh the entire contents of the
> "base" directory(which takes a VERY long time), whereas I am only
> interested in the contents of the 'com' directory. Evidently, defining
> filters on a source directory (Included and Excluded patterns) only
> affects what is shown in the Package Explorer AFTER everything is
> discovered, and not what is discovered and refreshed. Is there any way
> to configure Eclipse to only look at contents of the 'com' directory and
> ignore everything else under the "base"?
> I am trying to avoid having to modify the current ClearCase directory
> structure so to put the 'com' directory under another dedicated
> directory to narrow down the 'java source context'.
> Any insight will be very helpfull
>
Well, my first response would definitely be that the directory structure
is fundamentally poor - the source code for Java really should be at a
level below the project root.
But to address your question more directly, I'm curious why you feel the
Include/Exclude filters on Source Location are not what you need. They
are intended to do exactly what it sounds like you want - restrict
Eclipse to using only part of the Source Location. It may take a while
to do the initial build when first setting those, but that would be,
like someone else said, due to the inherently slow ClearCase view that
you are using.
Also, note that Eclipse does not generally support having workspace
contents on a non-local drive - the disk access is extremely frequent in
Eclipse, and mapped or network drives are going to have a noticeable
impact on the performance of the tool.
HTH,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.14149 seconds
Home