I agree that projects are defined for a reason. But I would like to be able to use refactoring and find usage across projects. That is very handing when doing framework projects, where you have the framework in one project and one or more dependent works in other projects.
/michael ----- Original Message ----- From: "Christian Andersson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 15, 2002 5:11 PM Subject: RE: [Eap-list] multi project support > > > My preference is to separate the projects, i.e. not mix files from several projects in one view. The projects are not configured to be separate projects without a reason. I could, however, really make use of the ability to _quickly_ swap between projects (i.e. the projects views) to be able to edit them (separately). > > Our company develop several interacting applications. Each application is a seperate project and when altering the communication interface of one application, you have to update other applications/plugins as well. Each application is built upon a common frame work and it would be great to keep that in a seperate project (yet still quickly accessible). > > /Christian > > > > part of the benefit, though, of multi project is that you > > could interact > > between the two projects without having to switch.. > > > > I know it's a bit harder to conceptualize (implement) but it would be > > cool if we could edit two source files from two different projects in > > one IDEA instance. > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
