[news.eclipse.tools] Towards improved CVS module support

[Michael Valenta <Michael_Valenta@xxxxxxx>]

One of Platform VCM's goals for 2.1 is to provide good CVS module 
support (by module support we mean supporting modules defined in the 
CVSROOT/modules file). We have identified a few areas we want to address 
but since we don't really use modules all that much, we are seeking 
input from people who do on any shortcomings that exist and/or 
improvements they would like to see (example use patterns/workflows are 
welcome too).

Some know issues we will be addressing are:

- Browsing of modules in "Show Modules" mode by version tag doen't work 
(see http://dev.eclipse.org/bugs/show_bug.cgi?id=22760).

- 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.

Some issues we will be investigating are:

- The use, display and expansion of modules in the CVS Repositories 
View. This will occur in conjunction with any Repositories View rework.

- The possible generation of module definitions from Eclipse.

If you have any ideas or comments on these issues or any additional 
issue you think are important, please reply.

Michael Valenta