If I remember correctly, the option disappeared long ago, when they started working at the modules part. And I don't remember reading about it being put back in, so the issue might not be fixed, yet.
Where did the option to save project paths relative to the project file path went in 977?
This has been answered somewhere else, but... here we go again. When concerning resources under the project root, all paths are saved relative to the project (module) root(s), and this has always been like this.
What "Save project paths relative to the project" option did was to save paths relative to the project even when the path is not under the project root. This option is now gone because it was rarely useful anyway.
We have several files come down on a "workspace initialization step", where the workspace contains 1 or more projects in their own directories, thus we have jar files that are in directories like /../lib
This is of extreme importance to us. Workspaces are shadows of the code base
and one can have them in various directories, hence the need for relative
paths.
Is there anything we can do to work around this?
Amnon
"Marcus Brito" ]]> wrote in message news:bqn6ep$1fs$2@is.intellij.net...
Amnon I. Govrin wrote:
>
Where did the option to save project paths relative to the project file
path
went in 977?
>
This has been answered somewhere else, but... here we go again. When concerning resources under the project root, all paths are saved relative to the project (module) root(s), and this has always been like this.
>
What "Save project paths relative to the project" option did was to save paths relative to the project even when the path is not under the project root. This option is now gone because it was rarely useful anyway.
If I remember correctly, the option disappeared long ago, when they started
working at the modules part. And I don't remember reading about it being put
back in, so the issue might not be fixed, yet.
Don't quote me on this, though. :)
Andrei
"Amnon I. Govrin" <agovrin@freshwater.com> wrote in message
news:bqlpja$ut2$1@is.intellij.net...
path
>
>
>
Amnon I. Govrin wrote:
This has been answered somewhere else, but... here we go again. When
concerning resources under the project root, all paths are saved
relative to the project (module) root(s), and this has always been like
this.
What "Save project paths relative to the project" option did was to save
paths relative to the project even when the path is not under the
project root. This option is now gone because it was rarely useful anyway.
--
MB
It will be back in the next build.
--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
"Amnon I. Govrin" <agovrin@freshwater.com> wrote in message
news:bqlpja$ut2$1@is.intellij.net...
path
>
>
>
Valentin Kipiatkov (JetBrains) wrote:
schmucks. spoiled my reply :P
Well, it is a must for us.
We have several files come down on a "workspace initialization step", where
the workspace contains 1 or more projects in their own directories, thus we
have jar files that are in directories like /../lib This is of extreme importance to us. Workspaces are shadows of the code base and one can have them in various directories, hence the need for relative paths. Is there anything we can do to work around this? Amnon "Marcus Brito" ]]> wrote in message
news:bqn6ep$1fs$2@is.intellij.net...
>
path
>
>
>
Yippee!!! I was worried for a moment (as you can see in my last post :)
Thanks,
Amnon
"Valentin Kipiatkov (JetBrains)" <valentin@intellij.com> wrote in message
news:bqnaq0$u8n$1@is.intellij.net...
>
>
>
>