| Unwanted Behavior: Eclipse Copying Files From Linked Resource [message #296532] |
Fri, 23 December 2005 11:20  |
Eclipse User |
|
|
|
Originally posted by: al.johnson.nagrastar.com
Greetings. I've read the documentation, searched Google and this forum and
haven't even remotely found the answer, so here it goes.
We are developing on Windows and using ClearCase served from a Unix box.
The mapped drive is very slow so to speed up my builds, I set the output
directory for class files (Java development) to an Eclipse folder linked to
a local drive folder. Works great until I restart Eclipse, at which time it
begins to copy all the files in the linked folder to a new folder of the
same name under the project directory which is on the slow mapped network
drive, thereby defeating the whole point of a linked resource. From this
point on, Eclipse ignores the linked folder as the default output folder and
uses this new one it created. In every way, the folder still looks like a
linked folder; even in the .project file. This has been EXTREMELY
aggravating. I've created the folder links both from the "create linked
folder" from the project Java Build Path properties dialog and from the
General/Workspace/Linked Resources dialog and the problem persists.
Is this a bug? By design? Is there a fix or workaround?
Thanks,
Al
PS, in every other way, Eclipse kicks major ass.
|
|
|
| Re: Unwanted Behavior: Eclipse Copying Files From Linked Resource [message #296843 is a reply to message #296532] |
Tue, 03 January 2006 11:47  |
| Eclipse User |
|
|
|
Originally posted by: al.johnson.nagrastar.com
Any comments or suggestions on this one?
"Al Johnson" <al.johnson@nagrastar.com> wrote in message
news:doh84a$tch$1@utils.eclipse.org...
> Greetings. I've read the documentation, searched Google and this forum
> and haven't even remotely found the answer, so here it goes.
>
>
> We are developing on Windows and using ClearCase served from a Unix box.
> The mapped drive is very slow so to speed up my builds, I set the output
> directory for class files (Java development) to an Eclipse folder linked
> to a local drive folder. Works great until I restart Eclipse, at which
> time it begins to copy all the files in the linked folder to a new folder
> of the same name under the project directory which is on the slow mapped
> network drive, thereby defeating the whole point of a linked resource.
> From this point on, Eclipse ignores the linked folder as the default
> output folder and uses this new one it created. In every way, the folder
> still looks like a linked folder; even in the .project file. This has
> been EXTREMELY aggravating. I've created the folder links both from the
> "create linked folder" from the project Java Build Path properties dialog
> and from the General/Workspace/Linked Resources dialog and the problem
> persists.
>
> Is this a bug? By design? Is there a fix or workaround?
>
> Thanks,
> Al
>
> PS, in every other way, Eclipse kicks major ass.
>
|
|
|
| Re: Unwanted Behavior: Eclipse Copying Files From Linked Resource [message #296922 is a reply to message #296532] |
Wed, 04 January 2006 14:44 |
| Eclipse User |
|
|
|
Originally posted by: john.eclipsefaq.org
That sounds like a bug. The scenario you describe was one of the main
use cases for linked resources when they were introduced. The link
should still be there when you startup the next session.
Can you please enter a bug report against Eclipse > Platform >
Resources. Some of the details you can provide:
- What build of Eclipse you are using (found under Help > About)
- Is the failure repeatable every time, intermittent, etc.
- Are there any errors in your log file on startup after creating the
linked folder?
- Do links disappear for a linked folder in the same project that is
*not* the output folder. I.e., does it only "lose" the link when linking
the output folder.
- Also, attaching the .project and .classpath files to the bug would
help to verify your setup.
--
Al Johnson wrote:
> Greetings. I've read the documentation, searched Google and this forum and
> haven't even remotely found the answer, so here it goes.
>
>
> We are developing on Windows and using ClearCase served from a Unix box.
> The mapped drive is very slow so to speed up my builds, I set the output
> directory for class files (Java development) to an Eclipse folder linked to
> a local drive folder. Works great until I restart Eclipse, at which time it
> begins to copy all the files in the linked folder to a new folder of the
> same name under the project directory which is on the slow mapped network
> drive, thereby defeating the whole point of a linked resource. From this
> point on, Eclipse ignores the linked folder as the default output folder and
> uses this new one it created. In every way, the folder still looks like a
> linked folder; even in the .project file. This has been EXTREMELY
> aggravating. I've created the folder links both from the "create linked
> folder" from the project Java Build Path properties dialog and from the
> General/Workspace/Linked Resources dialog and the problem persists.
>
> Is this a bug? By design? Is there a fix or workaround?
>
> Thanks,
> Al
>
> PS, in every other way, Eclipse kicks major ass.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05369 seconds
Home