Eclipse Community Forums: Newcomers » win7: .classpath does not support dir walk up?

Help

Home

Home » Newcomers » Newcomers » win7: .classpath does not support dir walk up?

Show: Today's Messages :: Show Polls :: Message Navigator

win7: .classpath does not support dir walk up? [message #1729816]

Tue, 19 April 2016 09:53

Frank Bergemann

Messages: 6
Registered: June 2010

Junior Member

i can't make it work to walk up the current directory for external jar files like this:

<classpathentry kind="lib" path="../../Component/third-party/oracle-jdbc/lib/ojdbc6.jar"/>

In linux it works.
Is there a different syntax for Windows?

Report message to a moderator

Re: win7: .classpath does not support dir walk up? [message #1729834 is a reply to message #1729816]

Tue, 19 April 2016 12:20

Eric Rizzo

Messages: 3070
Registered: July 2009

Senior Member

That's a relative path; what do you expect it to be relative to? The workspace? The project root? I'm not sure that's a good idea unless it is documented (API) what relative classpath entries are relative to.

Report message to a moderator

Re: win7: .classpath does not support dir walk up? [message #1729843 is a reply to message #1729834]

Tue, 19 April 2016 13:00

Frank Bergemann

Messages: 6
Registered: June 2010

Junior Member

well, it accepts paths like this also in windows:

<classpathentry kind="lib" path="./ext-resources/som-lib.jar"/>

So ./ is accepted as "current directory where .classpath is hosted".
I.e. ../ would be "one level up".

Report message to a moderator

Re: win7: .classpath does not support dir walk up? [message #1729845 is a reply to message #1729843]

Tue, 19 April 2016 13:05

Ed Merks

Messages: 33139
Registered: July 2009

Senior Member

Frank,

The point is that a relative path being relative to the project itself
makes sense and is obviously supported, but it's not clear where ..
should navigate to. Logically up to the root of the workspace?
Logically up to the physical file system folder of the project? There's
no guarantee that project X and project Y in the workspace can be
physically navigated by using ../Y from project X in the file system.
So if it's going to relative to the workspace, it would make more sense
to have some type of absolute way of refering to another project than
trying to accomplish that with a relative path that navigates up...

On 19.04.2016 15:00, Frank Bergemann wrote:
> well, it accepts paths like this also in windows:
> <classpathentry kind="lib" path="./ext-resources/som-lib.jar"/>
> So ./ is accepted as "current directory where .classpath is hosted".
> I.e. ../ would be "one level up".

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator