platform-vcm-home/docs/online/team2.0/team-faq.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (view) (download) (as text)

1 : kevinm 1.1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 :     <html>
3 :     <head>
4 : kevinm 1.2 <title>eclipse team 2.1 frequently asked questions</title>
5 : kevinm 1.1 <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
6 :     <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
7 :     </head>
8 :    
9 :     <body>
10 :    
11 :     <!-- Title -->
12 :     <table border="0" cellpadding="2" cellspacing="5" width="100%">
13 :     <tbody>
14 :     <tr>
15 : kevinm 1.2
16 :     <td align="Left" width="54%"> <font class="indextop">eclipse team 2.1 faq</font><br>
17 :     <font class="indexsub">frequently asked questions about the eclipse 2.1
18 :     team support</font> </td>
19 : kevinm 1.1 <td width="46%">&nbsp;</td>
20 :     </tr>
21 :     </tbody>
22 :     </table>
23 :    
24 :     <!-- Introduction -->
25 :     <table border="0" cellpadding="2" cellspacing="5" width="100%">
26 :     <tbody>
27 :     <tr>
28 :     <td align="Left" bgcolor="#0080c0" colspan="2" valign="Top"><b><font color="#ffffff" face="Arial,Helvetica">
29 :     Eclipse Team Component</font></b></td>
30 :     </tr>
31 :     <tr>
32 : kevinm 1.2
33 :     <td><font face="arial,helvetica,geneva" size="-1"> Last Modified: March
34 :     27, 2003</font></td>
35 : kevinm 1.1 </tr>
36 :     </tbody>
37 :     </table>
38 :     <br>
39 :    
40 :     <!-- Table of contents header -->
41 :     <table bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="0" width="100%">
42 :     <tbody>
43 :     <tr>
44 :     <td><font color="#000000" face="Arial,Helvetica" size="+1"><a name="toc">Table of contents:</a>
45 :     </font></td>
46 :     </tr>
47 :     </tbody>
48 :     </table>
49 :    
50 :     <ul>
51 :     <li><b><a href="#tips">Tips and Tricks</a></b>
52 :     <ol>
53 :     <li><a href="#tip_1">My project uses files that aren't in the default <i>text/bin</i> or <i>ignore</i> preference. How do I create my own list and share them?</a></li>
54 :     </ol>
55 :     </li>
56 :     </ul>
57 :    
58 :     <!-- End of table of contents -->
59 :    
60 :    
61 :     <!-- Tips and Tricks -->
62 :     <table bgcolor="#cccccc" border="0" cellpadding="2" cellspacing="0" width="100%">
63 :     <tbody>
64 :     <tr>
65 :     <td width="90%"><a name="tips"><b><font color="#000000" size="+1">
66 :     Tips and Tricks</font></b></a>
67 :     </td>
68 :     <td align="Right"><a href="#toc">top</a>
69 :     </td>
70 :     </tr>
71 :     </tbody>
72 :     </table>
73 :    
74 :     <!-- Tips and Tricks contents -->
75 :     <ol>
76 : kevinm 1.2
77 :     <li><b><a name="tip_1">My project uses files that aren't in the default <i>text/bin</i>
78 :     or <i>ignore</i> preference. How do I create my own list and share them?</a></b>
79 :     <p>Eclipse Team has a preference for denoting whether a new file added to version control should be
80 : kevinm 1.1 text or binary, and another preference to denote whether it should be ignored for version control.
81 :     These preferences are file name extension based.</p>
82 :    
83 :     <p>Eclipse ships with a default set. The set can be added to via extension points in org.eclipse.team.core.
84 :     (extension point ID's are <i>fileTypes</i> and <i>ignore</i> respectively).
85 :     This default set is not intended to be comprehensive: each plugin which introduces a new file type
86 :     should add to the list as appropriate.</p>
87 :    
88 :     <p>You may find that your team works with files which are neither in the default set nor are added
89 :     by another plugin. While you can add to the preference via the preference page, each team
90 :     member will have to do the same.</p>
91 :    
92 :     <p>Another way to build up your own list is to create a very small plugin that extends
93 :     these two extension points with the file patterns you care about.
94 :     This plugin can then be shared with your team; each team member simply needs to drop it into their /plugins
95 :     directory to get them. This also ensures you share the same set across different workspaces
96 :     which all use the same plugins directory.</p>
97 :     </li>
98 : kevinm 1.2 <p/>&nbsp;
99 : kevinm 1.1 </ol>
100 :     <br>
101 :     </html>