Even though all your source is in one big repository, can't you break your sourceball into multiple IDEA projects regardless of these sharing a common root package path like com.companyname? If some base packages are widely referenced, you can add these to the classpath of all your projects (in addition to the base having its own project) while keeping the source out.
Jon Guillaume Laforge wrote: > Hello, > > In my company, we have a quite big source repository, in which we store all > our source code. > It's about 25 MB. There are many projects inside this big directory. > But I have to put the root of this directory as my source path. > I know that I use certain classes, but not some others which are belonging > to other projects. > The problem is that each time I run IDEA, each time I'm making a search, a > "find usage", a refactoring, or whatever, it takes quite some time. And > quite some memory too ! > Could it be possible to allow to hide some directories that we know we don't > use in a certain project ? > It would be a kind of view of the tree. Some branches (never used in the > current application) would be just hidden. > There would be also a button to show or hide these directories. And IDEA > would know that it hasn't got to look into the hidden folders. > It would be different than in JBuilder which has a painfull virtual tree. > It's a pain in the... to deal with. > Especially compared with IDEA if we can restrict the source tree. > > What do you think about that feature ? Is it hard to implement ? Would you > find it usefull ? > > Guillaum _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
