Community
Participate
Working Groups
The support for content type detection in 3.0 has some shortcomings/bugs that need to be improved/fixed for 3.1. - Bug 69640 - associate content types to natures - Bug 79151 - cache is not discarded when file associations change - Bug 68270 - Encoding of property files - Bug 72023 - allow content type providers to specify additional default properties - Bug 72796 - findContentTypeFor ignores user file specs - Bug 57908 - should allow content types to added programmatically - Bug 56993 - make the content type registry dynamic Some PRs stating use cases that are not appropriately handled are: - Bug 78652 - content type should be bound hierarchically - Bug 78653 - Eclipse compare support does not appear to use file inspection correctly
Also: Bug 83004 - discontinue automagic aliasing
Also: Bug 85765 - allow users to disable content types
Also: Bug 86862 - need API for related custom objects lookup (required by bug 78652)
Also: Bug 87447 - support project-specific user settings
Also: Bug 90218 - review full/partial name matching policy
All issues addressed. Closing.