[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Release Notes for CDT 1.2
|
Well, I tried this on Linux and got the same result. The reason is that the
'getCanonicalPath' method of java.io.File resolves the links. When I replace
it by 'getAbsolutePath' everything works fine.
We are using 'getCanonicalPath' to as a workaround for PR 38468.
----- Original Message -----
From: "Alain Magloire" <alain@xxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Sent: Tuesday, October 07, 2003 4:55 PM
Subject: Re: [cdt-dev] Release Notes for CDT 1.2
> >
> > This is a multipart message in MIME format.
> > --=_alternative 006D9A0285256DB8_=
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Bug 43372 can be reproduced with eclipse 2.1.1 if you call eclipse with
a
> > -data option having a workspace path with a soft link. The workaround
> > would be to specify the workspace as a relative path (which doesn't
> > involve a link) or the full path of the actual location.
> >
> > Eg. call eclipse as:
> > ./eclipse -data /net/medusa/home/twolff/cdt/workspaces/ws1
> > instead of
> > ./eclipse -data /home/twolff/cdt/workspaces/ws1
> >
> >
>
> Interesting, are you using automount points(auto_fs) ?
>
> If the automounter when resolving the path is returning
> /net/hostname/home/... instead of /home/...
>
> I'm wondering if in automount point,
>
> IResouce.getLocation().toOSString();
>
> is returning a different value.
>
> Is this visible via the CDT/Debug only ?
>
> So for example if you do
>
> # /tmp/myworkspace
> # cd /home/twolff; ln -s /tmp/myworkspace workspace
> # eclipse -data /home/twollf/workspace
>
> You may have the same problem,(depending on the OS behaviour
> for symbolic links)
>
> >
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
