bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm - platform/eclipse.platform.common - Git at Google

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
 <HEAD>

 <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
 <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

 <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
 <TITLE>File types</TITLE>

 <link rel="stylesheet" type="text/css" HREF="../book.css">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
 <h3>File types</h3>
 <p>The presence of a repository management system may dictate special handling
 needs for files.&nbsp; For example, some files should be omitted from version
 control.&nbsp; Some providers have special handling for text vs. binary
 files.&nbsp; The team plug-in defines extension points that allow other plug-ins
 to provide information about their file types.&nbsp; In all cases, special
 handling is ultimately left up to the user via the team Preferences page.&nbsp;
 These extensions allow plug-ins to seed the preferences with values appropriate
 for the plug-in.</p>
 <h4>Ignored files</h4>
 <p>In several cases, it may be unnecessary to keep certain files under
 repository control.&nbsp; For example, resources that are derived from existing
 resources can often be omitted from the repository.&nbsp; For example, compiled
 source files, (such as Java &quot;.class&quot; files), can be omitted since
 their corresponding source (&quot;.java&quot;) file is in the repository.&nbsp;
 It also may be inappropriate to version control metadata files that are
 generated by repository providers.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
 extension point allows providers to declare file types that should be ignored
 for repository provider operations.&nbsp; For example, the CVS client declares
 the following:</p>
 <pre>&lt;extension point=&quot;org.eclipse.team.core.ignore&quot;&gt;
 	&lt;ignore pattern = &quot;.#*&quot; selected = &quot;true&quot;/&gt;
 &lt;/extension&gt;</pre>
 <p>The markup simply declares a file name <b>pattern</b> that should be ignored
 and a <b>selected</b> attribute which declares the default selection value of
 the file type in the preferences dialog.&nbsp; It is ultimately up to the user
 to decide which files should be ignored.&nbsp; The user may select, deselect,
 add or delete file types from the default list of ignored files.</p>
 <p><img src="images/ignore.png" alt="" border="0" ></p>
 <h4>Text vs. binary files</h4>
 <p>Some repositories implement different handling for text vs. binary
 files.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
 extension allows plug-ins to declare file types as text or binary files.&nbsp;
 For example, the Java tooling declares the following:
 </p>

 <pre>&lt;extension point=&quot;org.eclipse.team.core.fileTypes&quot;&gt;
   &lt;fileTypes extension=&quot;java&quot; type=&quot;text&quot;/&gt;
   &lt;fileTypes extension=&quot;classpath&quot; type=&quot;text&quot;/&gt;
   &lt;fileTypes extension=&quot;properties&quot; type=&quot;text&quot;/&gt;
   &lt;fileTypes extension=&quot;class&quot; type=&quot;binary&quot;/&gt;
   &lt;fileTypes extension=&quot;jar&quot; type=&quot;binary&quot;/&gt;
   &lt;fileTypes extension=&quot;zip&quot; type=&quot;binary&quot;/&gt;
 &lt;/extension&gt; </pre>

 <p>The markup lets plug-ins define a file type by <b>extension</b> and assign a <b>type</b>
 of text or binary.&nbsp; As with ignored files, it is ultimately up to the user
 to manage the list of text and binary file types.
 </p>


 <p><img src="images/filetypes.png" alt="" border="0" >
 </p>


 </BODY>
 </HTML>
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
	<HEAD>

	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
	<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

	<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
	<TITLE>File types</TITLE>

	<link rel="stylesheet" type="text/css" HREF="../book.css">
	</HEAD>
	<BODY BGCOLOR="#ffffff">
	<h3>File types</h3>
	<p>The presence of a repository management system may dictate special handling
	needs for files.  For example, some files should be omitted from version
	control.  Some providers have special handling for text vs. binary
	files.  The team plug-in defines extension points that allow other plug-ins
	to provide information about their file types.  In all cases, special
	handling is ultimately left up to the user via the team Preferences page.
	These extensions allow plug-ins to seed the preferences with values appropriate
	for the plug-in.</p>
	<h4>Ignored files</h4>
	<p>In several cases, it may be unnecessary to keep certain files under
	repository control.  For example, resources that are derived from existing
	resources can often be omitted from the repository.  For example, compiled
	source files, (such as Java ".class" files), can be omitted since
	their corresponding source (".java") file is in the repository.
	It also may be inappropriate to version control metadata files that are
	generated by repository providers.  The <a href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
	extension point allows providers to declare file types that should be ignored
	for repository provider operations.  For example, the CVS client declares
	the following:</p>
	<pre><extension point="org.eclipse.team.core.ignore">
	<ignore pattern = ".#*" selected = "true"/>
	</extension></pre>
	<p>The markup simply declares a file name <b>pattern</b> that should be ignored
	and a <b>selected</b> attribute which declares the default selection value of
	the file type in the preferences dialog.  It is ultimately up to the user
	to decide which files should be ignored.  The user may select, deselect,
	add or delete file types from the default list of ignored files.</p>
	<p><img src="images/ignore.png" alt="" border="0" ></p>
	<h4>Text vs. binary files</h4>
	<p>Some repositories implement different handling for text vs. binary
	files.  The <a href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
	extension allows plug-ins to declare file types as text or binary files.
	For example, the Java tooling declares the following:
	</p>

	<pre><extension point="org.eclipse.team.core.fileTypes">
	<fileTypes extension="java" type="text"/>
	<fileTypes extension="classpath" type="text"/>
	<fileTypes extension="properties" type="text"/>
	<fileTypes extension="class" type="binary"/>
	<fileTypes extension="jar" type="binary"/>
	<fileTypes extension="zip" type="binary"/>
	</extension> </pre>

	<p>The markup lets plug-ins define a file type by <b>extension</b> and assign a <b>type</b>
	of text or binary.  As with ignored files, it is ultimately up to the user
	to manage the list of text and binary file types.
	</p>




	<p><img src="images/filetypes.png" alt="" border="0" >
	</p>





	</BODY>
	</HTML>