[platform-vcm-dev] Breaking changes to IFileTypeRegistry

[James_Moody@xxxxxxx]

The interface IFileTypeRegistry has changed. This change will appear in 
the next integration build (*not* in 0312) and in the next milestone 
build.

The file type registry was originally designed as a generic table in which 
arbitrary keys and values could be stored and associated with file 
extensions. In particular, we use it to store information about file types 
that should be considered 'Text' and 'Binary'. We were considering moving 
it to a more generic place, as it seemed to be more useful than just a 
team-based table.

Our oversight was that by using keys (e.g. 'isText') and values (e.g. 
'true' and 'false), we run into trouble communicating those keys to 
providers. For example, CVS couldn't define keys because then JDT won't 
know about them.

The solution to this problem was to make the file type registry more 
specific to its actual usage, which is a storage place for whether or not 
files are to be treated as text. By removing the extension/key/value 
triplet, we've made it useful to a larger audience with fewer problems.

So,

-IFileTypeRegistry methods have changed. Implementers will have to update 
their code.
-The extension point format has changed. See 
org.eclipse.team.ui/plugin.xml for examples using the new format.

Thanks,

james