Re: [vuml] cvs repository structure
Status: Alpha
Brought to you by:
feradz
From: John R. <sd...@ya...> - 2006-12-09 14:29:36
|
Hi, Sorry for the tardy reply. As I said before, I'm new to Eclipse so I really have no idea how a project should be structured. I was basing my comments on 2 datums: 1). The cvs structure used by uDig. 2). Some error messages I was getting while trying to figure out how to launch vuml from within the workspace. I am now unable to reproduce these (so I was obviously doing something stupid). It is possible to just commit a sub-directory of a module using cvs. From the cvs man page: "If you don't specify particular files to commit, all of the files in your working current directory are examined. commit is careful to change in the repository only those files that you have really changed. By default (or if you explicitly specify the -R option), files in subdirectories are also examined and committed if they have changed; you can use the -l option to limit commit to the current directory only." I would still be inclined to separate the source directories into their own module (I'm a big fan of separating code, data and documentation), ending up with a structure like: --vuml---org.vuml | |-org.vuml-feature | |-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 What do you think? Best regards, John Ferad Zyulkyarov wrote: > Hi, > > I thought about your advice. I think that after rearranging the > project's CVS structure in the tree way that you propose, one may not > be able to select only particular projects to check-in. For example, > one may not wish to deal with the org.vuml.uml2.diagra.clazz project > (plug-in) that implements the class diagram editor. Actually, as I > noticed this is the way how eclipse's CVS is organized. Please, > correct me if I am wrong. > > |