Brian,

The only way to share preferences is to have one user export them and
have other users import them. Unfortunately, there is no way to limit
the export to just the Team file content settings. Another way to share
file content settings is by having them defined by a plug-in. That is,
you could write and install a plug-in that defined the file content type
for a particular file name pattern. The problem is that neither of these
approaches handle additions or changes to the settings well.

Another possibility is to set the line delimiters for your build file to
LF. You can set this property on the Jazz Source Control tab in the
file properties (i.e. open the Properties dialog from the context menu
of a file). Changing this setting will result in a change that can be
delivered and hence is shared with the rest of the team.

Michael

Brian Gillan wrote:

We have run into an issue where build scripts being edited and checked
in on Windows are causing problems when run on *nix machines because of
CR characters. It looks like the solution is to add the file type to the
Team File Content list. Is there any way to make this easy for an entire
team to pick up these definitions, either stored centrally somewhere, or
via an import?

Also, I recall the ClearCase remote client had a way to associate an
"extensionless" file type. Is this possible for the RTC client as well?

Thanks, Brian