You can add as many project paths as you want (which makes those files part of your project).
I think of the source path as a parallel to the class path. It tells IDEA where to look to find the matching java source files for the classes in my class path. They are used when navigating (like goto definition) and when debugging. There is something to be said for making the parallelism more explicit. One way would be to combine the source and classpath entries into a single list where each entry gave both where to find the sources and where to find the classes. This would fit in nicely with the request for per source tree compiler output paths since the output path for a source tree is by definition where to find the classes for that source tree. -- Mark -----Original Message----- From: Oliver Pfeiffer [mailto:[EMAIL PROTECTED]] Sent: Friday, October 19, 2001 10:11a To: [EMAIL PROTECTED] Subject: AW: [Eap-list] Re; 507 New Project Wizard Usability > 2. Source paths are the roots of java source trees. Only > these sources are visible during debugging. Only those > sources that are also below a project path are used during > recompilation. This pathes will be only used during recompilation if this pathes are subdirectories of the specified project directory. This is very pity because I often set my src path to directories outside of my project. So I have to compile all classes in this outsided files manually (because they aren't included in build project ): oliver _______________________________________________ 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
