Barry Kaplan wrote:
> These paths where not *just* in the idea/config files, but also in the
> project file itself. This essentially makes idea projects
> non-transportable in team development.
>
> I posted this earlier and got minimal responses. Is it really the case
> that hard coding of paths is a bother to most teams?
Hello Barry! Yes, that is bothersome. But there are some things you can do
to make it easier. If your project file is at or *above* the project root,
and not off on a branch, IDEA will automagically canonicalize any
references to the project root.
For example, one of my project files is in directory we'll call "foo". It
looks like this:
foo/
foo/ElgatoGui.ipr
foo/cdb/ (this is the project root, i.e., also the root of my checkout)
foo/cdb/build.xml
foo/cdb/lib/...
foo/cdb/src/...
foo/cdb/test/...
Notice the $PROJECT_DIR$ that IDEA inserted in my project file below.
Excerpt of ElgatoGui.ipr:
<?xml version="1.0" encoding="UTF-8"?>
<project version="2">
<component name="ProjectRootManager" version="2">
<jdk name="java version "1.4.1-beta"" />
<projectPath>
<root type="composite">
<root type="simple" url="file://$PROJECT_DIR$/cdb" />
</root>
</projectPath>
<sourcePath>
<root type="composite">
<root name="java version "1.4.1-beta""
rootType="sourcePath" ty
pe="jdk" />
<root type="simple" url="file://$PROJECT_DIR$/cdb/src" />
<root type="simple" url="file://$PROJECT_DIR$/cdb/test" />
<root type="simple" url="file://$PROJECT_DIR$/cdb/spike/siegetests"
/>
<root type="simple" url="file://$PROJECT_DIR$/cdb/spike/graphics" />
</root>
</sourcePath>
<classPath>
<root type="composite">
<root name="java version "1.4.1-beta""
rootType="classPath" typ
e="jdk" />
<root type="output" />
<root type="simple" url="jar://$PROJECT_DIR$/cdb/lib/junit3.7.jar!/"
/>
<root type="simple" url="jar://$PROJECT_DIR$/cdb/lib/radtest.jar!/"
/>
<root type="simple" url="file://$PROJECT_DIR$/cdb/resources" />
<root type="simple" url="file://$PROJECT_DIR$/cdb/test" />
</root>
</classPath>
Obviously, IDEA still needs to be fixed to make it work better in a
multi-user environment. I still keep my own project file, and the fact that
it uses a system-wide config directory is a real pain. Hey, at least it's a
tiny install so it's not a big problem to keep a few installs around.
Cheers,
Colin
Colin D. Bennett <[EMAIL PROTECTED]>
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
