[vuml] cvs repository structure

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I'm finding the current cvs repository structure with each
plugin/feature as a separate module somewhat cumbersome to work with.&nbsp;
Unless I'm missing something about how cvs works it is easy to miss the
addition of new modules when doing a cvs update as each new module
requires a separate checkout operation :-(<br>
<br>
Current structure:<br>
<pre>org.vuml				(plugin)
org.vuml.core				(plugin)
org.vuml.editor				(plugin)
org.vuml.examples.gettingstarted	(tutorial)
org.vuml.feature			(feature)
org.vuml.uml2.diagram.clazz		(plugin)
org.vuml.update				(update site web pages)
org.vuml.views				(plugin)
org.vuml.wizards			(plugin)

</pre>
Was there a reason for choosing the current structure? It might be
worthwhile restructuring the repository along the following lines
(which I have shamelessly adapted from another Eclipse project I am
involved with):<br>
<pre>--vuml---features---org.vuml.application
|      |          |-org.vuml.core
|      |          |-org.vuml.uml2.diagram.activity
|      |          |-org.vuml.uml2.diagram.class
|      |
|      |-fragments
|      |
|      |-plugins---org.vuml
|                |-org.vuml.core
|                |-org.vuml.editor
|                |-org.vuml.uml2.diagram.activity
|                |-org.vuml.uml2.diagram.class
|                |-org.vuml.views
|                |-org.vuml.wizards
|
|-documentation---programmers_manual
|               |-users_guide
|
|-tutorials---gettingstarted
|           |-more tutorials here :-)
|
|-update-site

</pre>
My reasons for suggesting this structure are:<br>
<ul>
  <li>All source code can be checked out or updated with a single cvs
command</li>
  <li>Going by some error messages I had when fooling around Eclipse
expects "Plug-ins must be in 'plugins' directory, and features in
'features' directory."</li>
</ul>
What do you think?<br>
<br>
Cheers,<br>
John<br>
</body>
</html>