In that case ( dependent projects ) isn't the artificially introduced boundary beneficial? We have the same situation here. One project is the core technology, and other projects are applications dependent on the core. I purposely build and jar my core project and use it as a library only in my dependent projects to make sure that I don't unwittingly change or refactor code cross projects therby creating problems for other dependent applications ( both in-house and ones built by our customers).
Don't get me wrong, I would love to be able to more easily switch between my projects so that when I *choose* to work in the core it is less painful. But I would definitely want to keep my actions confined to a single project. (usual "if its configurable then do whatever" disclaimer here) Brian Majewski Systems Architect Chrome Systems Corporation [EMAIL PROTECTED] PHONE: +1-503-963-6410 / +1-800-936-8906 FAX: +1-503-963-6312 www.chrome.com Notice: This e-mail transmission and/or the attachments accompanying it may contain confidential information belonging to the sender or Chrome Systems Corporation. The information is only for the use of the intended recipient. If you have received this transmission in error, please notify the sender immediately by reply e-mail, and then destroy all copies of the transmission. -----Original Message----- From: Michael Svinth [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 9:00 AM To: [EMAIL PROTECTED] Subject: Re: [Eap-list] multi project support 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 _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
