This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102468 - 'generic' source group should support project excludes too
Summary: 'generic' source group should support project excludes too
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Ant Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 114287 (view as bug list)
Depends on:
Blocks: 49026 101913
  Show dependency tree
 
Reported: 2007-04-25 11:47 UTC by Stanislav Aubrecht
Modified: 2010-04-02 20:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Aubrecht 2007-04-25 11:47:18 UTC 
at the moment 'generic' source groups contain all files under the project root.
however i think that files/folders excluded from the project shouldn't be in
these source groups.
Comment 1 Jesse Glick 2007-04-25 16:10:02 UTC 
SourcesHelper currently does not modify the implicit generic group according to
excludes specified in explicit groups which happen to be beneath it.

J2SESources calls addPrincipalSourceRoot with appropriate includes and excludes
for each JAVA-type root, whether or not it is external, so it should suffice for
SH to only pay attention to untyped roots. Needs to be confirmed that freeform
projects will also behave properly in this respect (when configured through the
GUI).

JDK's j2se/make/netbeans/common/*-sources.ent currently do not mark excludes on
untyped source roots, at the request of folks who specifically wanted to see
everything in the Files tab. Can probably be changed.
Comment 2 Jesse Glick 2007-10-26 19:36:40 UTC 
*** Issue 114287 has been marked as a duplicate of this issue. ***
Comment 3 Jesse Glick 2007-10-26 19:39:00 UTC 
Probably too risky to make such a significant change this late.
Comment 4 Jesse Glick 2010-04-02 20:18:51 UTC 
No known use case, and potentially detrimental to performance.