IMO the right way to soplve this is to put the packages with wich you work in one source tree and all the rest in another. Specify yours files as _project_ and the other set as _source_ folder. You can switch between them using the dropdown in the Project View.
The drawback is that if you have ant scripts which build the entire tree they wouldn't work, that's why you could keep an old copy of your classes in the Sources folder and build from idea, when you commit your Project folder, you can synchronize the Sources from CVS. -- dimiter "Guillaume Laforge" <[EMAIL PROTECTED]> wrote in message adfv6k$o2u$[EMAIL PROTECTED]">news:adfv6k$o2u$[EMAIL PROTECTED]... > Well, thanks for the info, I'll tell my colleagues they can use this open > tool... > But honestly, I don't want to use JBuilder anymore, I only wanna work with > IDEA. > So, if I may suggest some improvements for IDEA, I'm asking :o) > > I think the ability to offer IDEA a view on your source tree or project > tree could be very usefull (and not to hard to implement). > It would save a lot of time, and consume less memory each time you need to > perform a search or even at startup time. > It would also avoid to create local copies of all jars, and so on... > > Guillaume > > > "Andrew Sazonov" <[EMAIL PROTECTED]> a �crit dans le message news: > [EMAIL PROTECTED] > > Just two cents: > > > > In JBuilder you can solve this problem if you install free open tool > > named SmartNodes. It allows to filter content of any package using > > regular expression. > > > > Best regards, > > Andrew Sazonov > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
