blob: 85cea3dd2ed48e75e738cc9fcdd34c1b8ed46fa9 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Proposed CVS Modules Support for 2.1</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
</head>
<body bgcolor="#ffffff" text="#000000">
<p>Back to <a href="../archivedReleases.php">Archived Releases</a></p>
<table border="0" cellspacing="5" cellpadding="2" width="100%">
<tbody>
<tr>
<td align="left" valign="top" colspan="2" bgcolor="#0080c0">
<b><font color="#ffffff" face="Arial,Helvetica">
Proposed CVS Modules Support for 2.1
</font></b>
</td>
</tr>
<tr>
<td align="right" valign="top" width="2%">
<img src="http://dev.eclipse.org/images/Adarrow.gif" border="0" height="16" width="16">
</td>
<td width="98%">
<b>Know issues we will be addressing are:</b>
<ul>
<li><b>Done:</b> Browsing of modules in "Show Modules" mode by version tag doen't work
(see bug <a href="http://dev.eclipse.org/bugs/show_bug.cgi?id=22760">22760</a>).</li>
<p/>
<li><b>Done:</b> It is difficult to work with Java packages that are defined at the
root of a repository because Eclispe requires packages to be children of
a project. The current workaround is to define modules in the
CVSROOT/modules file. We would like to simplify this by supporting the
checkout of a folder into an existing project shared with the same
repository.</li>
<p/>
<li><b>Done:</b> By default, the "cvs update" command is always performed with the
-d option which discovers new or previously unknown directories and loads their contents.
A property could be added to each project which enables/disables the use of the -d option.</li>
</li>
<p/>
<li><b>Will not be done:</b> Eclipse will automatically purge the CVS folders from any folder that
is moved. This behavior could be enhanced as follows:
<ol>
<li>If the folder is moved to a project that is not shared with a
repository, the project could be configured such that CVS operations
performed on the project would only effect the moved folder.</li>
<li>If the folder is moved to a project shared with the same repository,
the folder could be added and the CVS folders maintained.</li>
<li>If the folder is moved to a project that is mapped to another CVS
repository or another repository provider, the CVS directories must be
purged.</li>
</ol>
For case 1 and 2, the user would be prompted to carry out the operation
or purge the CVS information.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</body>
</html>