sunuml-developers

[Sunuml-developers] Proposed SVN repository structure

[Aidar T. <ata...@ya...>]

root
   trunk
      sunuml              - core SunUML project
      plugins              - plugins we will be developing like reverse-engineering and code generation etc.
      help                  - interactive help and documentation
      installer             - installer project
      3rdparty             - third party software we use
      build                  - build related scripts/configs etc.
      <other projects> - we will create similar directory for other projects we decide to create.
   tags                     - tags/branches for the projects above.
   branches

In that layout one checks out trunk and gets a working copy of the projects, un-needed tags and branches are not checked out.

Let me know what you think.

Regards,
Aidar aka AIDS


      

Re: [Sunuml-developers] Proposed SVN repository structure

[Steven G. <laz...@gm...>]

Seems ok.

1 -I added it on the wiki feel free to modify it and discuss what you don't
like here.
http://sunuml.wiki.sourceforge.net/Project+Structure


2 - I suggest one modification: adding a 'sunuml' folder at the base.
This replace the concept of cvs modules and permit us -even if we don't do
it- to add a whole new project.
Without it would be difficult to do it afterwards.

Such as an eclipse plugin which has a different code base/structure etc.


3 - I prefer 'doc' instead of 'help' because I would also put the api doc in
it.
But I don't mind.


4 - I am less sure about '3dparty'. What do you mean?
Whole softwares? In this case we most certainly can't distribute them
easily.

Or do you mean the dependencies libraries?
In this case I just got a doubt: can a folder *begin *with a number for all
platforms & languages?

Why not simply '*libs*' ?


5 - I would add a root/trunk/bin folder where the exe are put and the
dynamic libs are copied.


Steven