I asked a similar question recently in this group, and didn't get any
response, so here it goes again:
Suppose I have my local source directories arranged like this:
I have IDEA projects for sharedlib, componentA, and componentB. Both
componentA and componentB depend on sharedlib. I have defined a Library
in IDEA named "sharedlib", which is referenced in the .ipr files for
both componentA and componentB.
My source code is stored in a branch-capable SCM like CVS, etc. The
project files (.ipr) are stored in CVS.
Some time after release 1.0 of my product, I need to make some bug fixes
to the 1.0 release. The 1.0 release is now on a branch, with the main
trunk being ongoing 2.0 work. So, I check out the 1.0 branch into a
separate local directory, let's say, "branch". My branch source tree
Now, the .ipr files in branch/componentA and branch/componentB both
refer to a Library named "sharedlib". However, currently (in Ariadna),
library definitions can only hold absolute paths, so, I'm screwed. I
cannot safely build from this branch because the "sharedlib" Library
definition referenced by "componentA/componentA.ipr" and
"componentB/componentB.ipr" refer to "/src/sharedlib" whereas I need it
to refer to "/branch/sharedlib" (actually what I really need is for the
Library definition to refer to "../sharedlib"- this would enable me to
check out my source to whatever local directory I wanted to).
I thought Aurora would add relative path capability in Library
definitions, but, my current understanding is that only Project Library
definitions can hold relative paths. Since Project Library definitions
are stored in the .ipr file, I cannot share the definition of a
"sharedlib" Project Library between componentA and componentB- I have to
redefine it in each project.
JetBrains gurus- is my understanding correct? Will there be any way in
Aurora to have relative paths in Global Library definitions? If not,
doesn't this common use-case argue that Aurora needs this capability?
Thanks for any advice-