I agree with Amnon. In our development shop usually the teams have a common project layout. In addition some of our teams are producing frameworks that other teams use. In both cases it would be nice to be able to set some run/debug configuration to go in the project file. Case of the framework: a template project file would be offered to framework users to jump start their app development. In the case of different members of the same team, changes in the run configuration would be immediately picked up by others.
Again we are touching on the scalability issue of IDEA in the context of large teams/multiple dependent teams. Realize that we have close to 200 developers and everything that can enhance communication between teams and inside teams is a tremendous gain. This problem doesn't stop at run/debug configuration. * Class templates, live templates (framework developers should be able to distribute their framework templates along with their framework. Same team members should be able to share them as well) * Additional java tags (we use xdoclet on some of our projects) * Library/jdk tables: * Todos All these files need to be manage through the VCS as other project files (checkout on modification, check in project,...) Jacques "Amnon I. Govrin" <[EMAIL PROTECTED]> wrote in message amd6tp$ff0$[EMAIL PROTECTED]">news:amd6tp$ff0$[EMAIL PROTECTED]... > OK, I suggest that since it is obviously a controvertial point and there are > voices from each side, allow it to be in the ipr if wanted (e.g. have a > checkbox to save in project file) so that we can check in only the ipr. The > current state is that we simply have to check in the iws because of that. > > Thanks, > Amnon > > "Thomas Singer" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I agree with Eugene. There are just a small number of main entry > > points into an application, but there might be a large number of > > main-classes, that are called only in a very special meaning, e.g. > > when running a special test case. > > > > Why user B should have all Run/Debug configurations, that only user A > > needed to fix bugs x, y and z? > > > > Tom > > > > > > On Wed, 18 Sep 2002 22:56:55 +0400, "Eugene Zhuravlev" > > <[EMAIL PROTECTED]> wrote: > > > > > Well, I would disagree. Generally different members of a team run/debug > > > different tasks (tests for example or various configurations of the same > > > program) and thus may have different numbers of run/debug entries. This > > > should not be shared together with the common project structure. > > > > > > -- > > > > > > Best regards, > > > Eugene Zhuravlev > > > JetBrains, Inc, http://www.intellij.com > > > "Develop with pleasure!" > > > > > > > > > "Amnon I. Govrin" <[EMAIL PROTECTED]> wrote in message > > > ama8aj$9nc$[EMAIL PROTECTED]">news:ama8aj$9nc$[EMAIL PROTECTED]... > > > > Hi, people. > > > > > > > > If you agree with #4090, please vote for it. > > > > > > > > Here is a transcript: > > > > In my opinion, running and debugging entries (RunManager > component)should > > > be > > > > in the ipr and not iws file. > > > > It seems that the ipr contains global project settings (paths, output > > > > directory, etc.) and iws contains user-related settings (e.g. > SourceSafe > > > > integration). > > > > I think that running and debugging entries fall in the global category > > > since > > > > the project is run the same way every time (at least for everyone in > the > > > > project that I am part of). If it weren't for this, we would have > checked > > > > only the ipr in, but now we are forced to check in the iws as well > which > > > > causes many problems (e.g. if the SourceSafe settings are set). > > > > Please take care of this, I hope it makes sense and that I am not > alone. > > > > > > > > Thanks! > > > > > > > > Amnon > > > > > > > > > > > > > > > > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
