Login | Register
My pages Projects Community openCollabNet

argouml
Wiki: Github-based development environment

Edit this page | Links to this page | Page information | Attachments | Refresh page

 

This is an attempt to outline what the structure would be if the argouml-source repository would move to Github.

Git-Repositories to set up

One per tigris-project:

  • argouml
  • argoprint
  • argouml-andromda
  • argouml-cpp
  • argouml-csharp
  • argouml-db
  • argouml-de
  • argouml-documentation
  • argouml-en-gb

... The contents is everything from trunk except for the trunk/www part.

Two ways to do this:

  1. Keep the history. Convert every commit, create tags from tags and branches from branches. Branches/tags from releases would probably be a good thing to keep too but this has to be tested.
  2. Abandon history. The history is still at Tigris for those that want to dig into that.

Toolchain

The existing ant-based build chain will not work anymore. Especially the release script that is very much subversion-oriented will not work. Luckily we have already done some work with maven-builds.

Suggestion for tools:

  • maven (hopefully most in place)
  • github + gerrithub (create, upload, configure)
  • ad.hoc. build server (who manages this, configure and maintain)

Work to be done and suggested order:

  1. Announce the work.
  2. Transfer the contents of the argouml.tigris.org project (the main project).
    1. Move all the code into the repository at github.
    2. Resolve the testmodels problem by keeping a copy.
    3. Remove the code from the tigris repository.
  3. Transfer the contents of the argouml-actionscript3, argouml-cpp, argouml-csharp and argouml-java projects.
  4. Announce that development can continue in the main repositories.

After this the work has several independent tracks:

Get the argouml/tools/maven/toppom.xml builds to work moving it to separate repository.

Transfer the contents of each of the rest of the projects

Maven-based releases.

Set up repo. Describe how to work with repo.

Set up gerrithub.

Get them to build individually adding each to the repo configuration.

Modify the repo configuration to point to gerrithub.

Describe how to do development using gerrithub.

Set up build server.

Check that developing using Eclipse works (egit against gerrithub).

Github-based development environment (last edited 2018-05-19 05:57:15 -0700 by linus)