well, given that any folder with a script in it could be considered a source folder
The point is that you sometimes do not want some scripts to be processed. For example, they may be template files you use to generate code, or platform- or configuration-specific files you don't need at the moment, ones that would cause unneeded errors to appear or navigation to provide irrelevant matches if processed by the builder.
BTW, why do you need to skip "etc" in your particular case?
i guess what i would like to see here is a way for the project root (and only the project root, no sub-dirs beneath it) to automatically be considered as a source folder when it came time to build type operations without the user having to explicitly specify it as such.
You can add that to your project creation wizard, or am I missing something?
On Mon, Sep 22, 2008 at 10:26 PM, Andrey Tarantsov <andreyvit@xxxxxxxxx> wrote:
Jae,
The whole point of source folders is to define what to process as source code (and, thus, what to build).
You can configure source folder exclusions so that "etc" get excluded, but everything else is included. If this is not enough (for whatever reason), we should be discussing ways to change source folders, but *not* ways to allow building sources outside source folders.
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
-- -jae
|
