Re: [vuml] cvs repository structure
Status: Alpha
Brought to you by:
feradz
Menu
▾
▴
Re: [vuml] cvs repository structure
|
From: John R. <sd...@ya...> - 2006-11-28 11:21:11
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body>
Hi,<br>
<br>
Unfortunately I am no cvs expert either :-( If you don't have any luck
with the sourceforge admins I could ask the GRASS-GIS folks for some
advice. They restructured their repository a while back.<br>
<br>
If restructuring cvs is too difficult another option might be to leave
cvs as is and migrate the restructured code to subversion...<br>
<br>
Cheers,<br>
John<br>
<br>
Ferad Zyulkyarov wrote:
<blockquote
cite="mid...@ma..."
type="cite">
<pre wrap="">Hi,
at the time when I was initiating the project I hadn't much experience
with CVS. So this organization happened to be accidentally :( Your
advice about the organization is quite reasonable. I would change it
but, with sourceforge it is very heavy procedure. I have to write the
admins and explain them for the details.
Ferad Zyulkyarov
On 11/27/06, John Reid <a class="moz-txt-link-rfc2396E" href="mailto:sd...@ya..."><sd...@ya...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Hi,
I'm finding the current cvs repository structure with each plugin/feature
as a separate module somewhat cumbersome to work with. 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 :-(
Current structure:
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)
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):
--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
My reasons for suggesting this structure are:
All source code can be checked out or updated with a single cvs command
Going by some error messages I had when fooling around Eclipse expects
"Plug-ins must be in 'plugins' directory, and features in 'features'
directory." What do you think?
Cheers,
John
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</a>
_______________________________________________
Vuml-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Vum...@li...">Vum...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/vuml-general">https://lists.sourceforge.net/lists/listinfo/vuml-general</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
|
