Sharing ipr and related files

I understand why I can't share the .iws files, but it seems that I am unable to share the ipr files because the run configurations use absolute paths. Is there any way to put a path variable in the run configuration to specify a relative path from the project file?

Also, I need to put the hostname on my command line argument, and it would be useful if there was a way to specify an environment variable.

Anyone else run across these problems while attempting to share project files?

Mike

5 comments

Hello Michael,

MK> I understand why I can't share the .iws files, but it seems that I
MK> am unable to share the ipr files because the run configurations use
MK> absolute paths. Is there any way to put a path variable in the run
MK> configuration to specify a relative path from the project file?
MK>
MK> Also, I need to put the hostname on my command line argument, and it
MK> would be useful if there was a way to specify an environment
MK> variable.
MK>
MK> Anyone else run across these problems while attempting to share
MK> project files?
MK>
MK> Mike
MK>
Did you try the Macro Path from the Settings?
Did you turn on relative paths in the Paths in Settings?

Jacques

0

The run configurations are stored in the workspace file (*.iws), so it isn't really feasible to share.

We are sharing the *.ipr and *.iml files, but ran into several other problems, the most annoying being CVS conflicts and unnecessary merges.

0

Yep - they still haven't quite got this one sorted :( We now find we can
share the .iml files (using all relative paths) but each developer has his
own .ipr and .iws files. They really just don't share. What really needs to
happen is:

.iml - stays as it is - all relative paths

.ipr - contains all project settings - all relative paths - pretty much
stays as it is?

.iws - contains only "local" settings (last locations of dialogs, etc) -
does not contain run configurations

.ip? - contains run configurations (all relative paths)

The reason to separate out run configurations is that you can then decide
whether you want to share them or not. At present you can't (because the
.iws is not sharable). The .ipr is sharable at the moment but still contains
things that developers might set up differently (at least we find that to be
the case!).

Cheers,

TicH



0

Did you try the Macro Path from the Settings?


What are these? Can i use them from the run configuration dialog (the help doesn't even indicate how to use them). Even if I could, I still need to go manually update this, and I think that is basically the problem.

Did you turn on relative paths in the Paths in
Settings?


Yes..But it doesn't solve all the problems.

Mike

0

Yep - they still haven't quite got this one sorted :(


So, I should probabaly write a tracker problem that indicates:

- Run configurations should be separated from ipr and stored relative to the project file.
- There should be away to specify an environment variable (i.e. hostname).

Are there any other shortcommings that would be useful? I'll put them all together in the same tracker..

Mike

0

Please sign in to leave a comment.