Hi Martin, That's right, it's possible to choose the packages individually and add them to your source path or your project path, but I feel it's not really as convenient as importing just the root, and then removing the "branches" (sub-packages) you wish not tu use, or that you know your project doesn't need at all. With IDEA, I become more and more lazy ;o) That's why I think it'd be an interesting feature to be able to make a kind of "view" of the source tree by removing unused branches. Anyway, thanks for the suggestion, and I'm happy to see that there is at least one person who agrees with me that it is a bit painfull to tweak the list of packages each time you want to increase a scope, or each time you want to create a new package :o/ Have a nice day,
Guillaume "Martin Bayly" <[EMAIL PROTECTED]> a �crit dans le message news: [EMAIL PROTECTED] > Isn't this already possible in IDEA by tweaking which packages you add > to your "project" path. You need to add the root of your companies > source repository as your "source" path so that the package hierarchy is > resolved correctly. However, IDEA uses the Project path not the source > path for find usages and refactoring. You can add individual packages to > the project path and that should limit the scope of IDEA's usage searches. > > I use this currently. Its a bit of pain at the moment if you want to > increase the scope of any given usage search, as you have to edit your > project paths. So a feature that allowed you to quickly enable/disable > particular project paths would be useful, to enable you to quickly > change the scope of usages searches/refactorings. > > Cheers, > Martin _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
