Why are Run Configurations defined in .iws file?

Why are Run Configurations defined in .iws file? It's very inconvenient because I want to share them along with the project, but I don't want to share the other stuff in the .iws file. I can't imagine I am the only one in this situation. Since run configurations are often associated with a project, it makes sense to me to store them in the .ipr file or even a separate file altogether for people who don't want to share the run configurations. Anything is better than the current situation where I am forced to check in the .iws file, most of which is irrelevant to other users.

Any plans to change this in the future releases?
Thanks in advance.

6 comments
Comment actions Permalink

We've chosen to store run configurations in iws files because they change
quite often at least due to JUnit tests.
-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

Why are Run Configurations defined in .iws file? It's very
inconvenient because I want to share them along with the project, but
I don't want to share the other stuff in the .iws file. I can't
imagine I am the only one in this situation. Since run configurations
are often associated with a project, it makes sense to me to store
them in the .ipr file or even a separate file altogether for people
who don't want to share the run configurations. Anything is better
than the current situation where I am forced to check in the .iws
file, most of which is irrelevant to other users.

Any plans to change this in the future releases?
Thanks in advance.



0
Comment actions Permalink

Maxim Shafirov (JetBrains) wrote:

We've chosen to store run configurations in iws files because they
change quite often at least due to JUnit tests.


Maybe add a checkbox to the run configuration dialog which determines
whether a particular configuration is saved in the project file?

It could default to unchecked -- store in iws -- so that users can add
configurations without worrying about changing the project file, and
only when they want to specifically export a configuration do they check
the option.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001

0
Comment actions Permalink

Gordon Tyler wrote:

Maxim Shafirov (JetBrains) wrote:

>> We've chosen to store run configurations in iws files because they
>> change quite often at least due to JUnit tests.


Maybe add a checkbox to the run configuration dialog which determines
whether a particular configuration is saved in the project file?


It seems to me that the level of sharing of configuration could be
improved, and run configurations is one of the common culprits. Another
one is the JDK setup. People very often need to manually recreate these
settings. The problem appears to be that there are user-specific
details that are required. For the JDK, obviously the path to the JDK.
For run configs, it depends on the type, but often working directory and
other user-specific paths and ports.

It seems like it should be possible to partially configure these things
and share the partial configuration. You can think of it as an
'interface' to the configuration. E.g. "To compile, you need a JDK
compatible with version 1.5." So, the user has to locate such a JDK, but
the name of the JDK config, plus the fact that it requires tools.jar, or
whatever other non-user-specific details, are all part of the shared
configuration. Tomcat/Weblogic could also be partially configured this
way too. It would at least give your team members most of the
configuration, and also give them information about what parts of the
configuration are missing. Currently, all of this must be shared
informally, such as by email or word-of-mouth, etc.

--
Rob Harwood
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Yes exactly. Currently, if I want to share my project with team members, I have to write instructions like this:

1) Open project.
2) Set up path variables (describe how)
3) Set up JDK (describe how)
4) Set up Tomcat (describe how)
5) Set up Run configurations (describe how which takes long time because there are many of them.

Ideally, I should be able to specify Run configurations in .ipr file, or export them and have the others import them. It would also be nice if upon opening a project with missing information other engineers would get one dialog where they can specify one time:

1) JDK Path.
2) Tomcat Path.
3) Path variables.

etc, whatever else is missing.

Currently sharing project is hard. Path variables feature helps somewhat but it's kinda broken in 5.0.0 (thankfully the bug has been fixed in 5.0.1).

0
Comment actions Permalink

Ilya wrote:

Yes exactly. Currently, if I want to share my project with team members, I have to write instructions like this:

1) Open project.
2) Set up path variables (describe how)
3) Set up JDK (describe how)
4) Set up Tomcat (describe how)
5) Set up Run configurations (describe how which takes long time because there are many of them.

Ideally, I should be able to specify Run configurations in .ipr file, or export them and have the others import them. It would also be nice if upon opening a project with missing information other engineers would get one dialog where they can specify one time:

1) JDK Path.
2) Tomcat Path.
3) Path variables.

etc, whatever else is missing.

Currently sharing project is hard. Path variables feature helps somewhat but it's kinda broken in 5.0.0 (thankfully the bug has been fixed in 5.0.1).


This has been a standing issue ever since the ipr got split (initially
to ipr and iws, then the iml files came along).

Rob and JetBrains, it would be very useful to have the option to have
run/debug environments as project or not.

Amnon

0

Please sign in to leave a comment.