Community
Participate
Working Groups
Allow export exclusion for source folders for a project in project properties -> 'Build order and export' (and not only for used libraries). That would allow to create several source folders for one project, but hide some source folders from other projects which depend on this project.
This can easily be accomplished by dividing your project into 2 separate projects.
We are considering associating a project with some restriction patterns for its contributed classfiles. For instance, you could say that as an Eclipse developper, you want to hide all types defined in '**/internal/**' to your dependent projects (as these are non API types). Would this do the trick ?
Same feature as for source folders ? I think that would do it, but it would be very useful to also have excludes AND includes - like for source folders.
I think exclusion/inclusion filters for class folders would also be useful. I have a few scenarios where configuration files on the classpath are brought in as class folders into a project (and exported to dependents). Some of these have a nested folder structure, with the parent and child folders individually listed on the classpath (It's icky, I know). Class folder filters would make handling this easier.
Created bug# 73389: Inclusion/exclusion filters for class folders
*** This bug has been marked as a duplicate of 29865 ***