Community
Participate
Working Groups
The 'Java|Compiler|Other|Filtered resources' tab of the Preferences allows some resource types to be filtered and not output to the build location as part of the build. This is useful for things which need to be in revision control, but not be output into the build (one example is TogetherJ metadata, *.df*). This setting however needs to be project specific, not user specific. It's not great for every team member to have to manually add these filters. Best would probably be to have both project and user specific settings for this.
Defer
Reopening
Clearing resolution
All 'Java|Compiler' preferences needs to be project specific, at least 'Classfile Generation' and 'JDK Compliance', if you are developing for different platforms (PC<->embedded).
Along with per project settings.
Duplicate of bug 7091 *** This bug has been marked as a duplicate of 7091 ***
Solved in latest, still need UI to surface it.
I don't know why this bug is marked resolved or a duplicate of 7019, because neither seems correct in Eclipse 2.1.2. I was logging in to report this same bug when I found this bug. It is very important to us that various files not be copied into the bin directory, since they are not part of what we want to ship (they are "hidden" files related to the source control system). Also, we have multiple "source folders" per project, each with the same Java package structure below it, so the duplicate-named files in them are producing the error "The resource is a duplicate and was not copied..." during a build. It is also very important that the "filtered resources" field be saved into the ".project" file, not the user's workspace. The team is sharing the project and classpath files via source control, and there is no good reason why filtered resources should just be per-user. There are already numerous settings that unfortunately have to be manually set per user (like using spaces instead of tabs) but this one is particulary bad as it results in different users producing different builds from the same project files... it is illogical for it to be OK for one user to put certain files in a build but not for another user to do so -- it must be project-specific. Please either reopen this or explain how it has been "resolved" because we are using 2.1.2 and it is clearly not fixed. If you mean it is fixed in 3.0, we can't move to that yet. (I doubt you mean it is fixed in 3.0 because the bug was closed 1.5 years ago, long before any 3.0 was around.) Thanks.
