Hi Thomas, I would like to suggest maintaining both a Git and an SVN. Yes, it's tedious. But before going into that, here's a few links of Git vs SVN comparison.
- https://git.wiki.kernel.org/index.php/GitSvnComparison (Git's own view) - http://thinkvitamin.com/code/why-you-should-switch-from-subversion-to-git/ (Blog post) - http://stackoverflow.com/questions/161541/svn-vs-git (Stackoverflow post) Back to maintaining a Git and SVN, which is tedious, but could be theoretically made simpler via shell scripts or some scripts or tools. A suggestion is to continue using SVN as the main, but every update onto the SVN, you may want to have a prepared script that would simply launch on a double click and would grab the latest SVN and clone onto Git. This isn't very elegant sounding but it reduces the work overhead. Another way is to manage both Git and SVN personally and may include the use of scripts and build tools to support both. Git support is better off without Java plugin support as of now as the Java plugins are poorly made to my opinion. I personally have a project that runs Mercurial, Bzr and Git because Launchpad (Ubuntu) supports Bzr account, Mercurial for other accounts and a Git for other accounts to distribute the project to wider audiences. It is not efficient since I had to commit to three repository and push them but that's what happens if the project wants to be made highly accessible. Each of the accounts support a certain set of repository so it's better to have whatever it takes to get it done. It's not elegant though (for my personal solution) but it works. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
