Summary: | Provide facility to exclude files from compilation | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Amelia A Lewis <amyzing> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | avijayr, quartz12h, ric.almeida, zac_is_cooler_than_vince |
Version: | 2.0 | ||
Target Milestone: | 2.1 M4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Amelia A Lewis
2002-07-30 10:57:54 EDT
Would such excluded files be excluded from building only, or not available completely (search, code assist, package view, etc...). I'd say that minimal functionality for the feature would be to suppress building only. If the information was supplied to the plugins, then they might allow further customization (hide it if it won't be compiled). This might be permitted in the package view as an option, or possibly an icon decoration in the tree. Note that if it isn't compiled, then it can't *contribute* to code completion. I don't see why code completion (of other defined interfaces and such) inside the editor, when the file is open, would be suppressed. What you mean is that these files would not be treated as compilation units but rather as resource files. This means, they would not get compiled, indexed for search and presented in the package view (except as non-java resources). At least this story would be consistent. You can experiment this minimalistic behavior by copying a java file outside the classpath. You can still open it in a Java editor and perform some Java actions on it, but with minimal support of course. *** Bug 22409 has been marked as a duplicate of this bug. *** *** Bug 24583 has been marked as a duplicate of this bug. *** *** Bug 24127 has been marked as a duplicate of this bug. *** Exclusion filters got added to source folder, providing this ability. UI for it is on its way (for 2.1M4). Fixed. Verified. |