SCM-Manager 2.0.0-rc4

For some time, the incompatability of SCM-Manager 2 with Java 9 or above has annoyed us. Now we can happily announce, that this is history. With the new version 2.0.0-rc4 SCM-Manager can run on Java 9 and above.

A little error though has not made it into this release: If you are hosting mercurial repositories, you cannot create new commits, when XSRF protection is enabled. This is no new bug in this version and if you haven’t come accross it with previous releases, it should be of no relevance for you (this should be relevant only if you are using the editor plugin with mercurial repositories). This bug will be fixed in the next release.

Get the new version

You can download the RC-4 here

  • .tar.gz (sha1: 7aa87cec712335b93b0cbc49333c5fc9edd26fdc)
  • .zip (sha1: 603cf76d7d685951533ad19f5e1aa990607ec3bf)

or use it via Docker

docker run -p 8080:8080 -v scm-home:/var/lib/scm --name scm scmmanager/scm-manager:2.0.0-rc4

2 Responses to SCM-Manager 2.0.0-rc4

  1. Gibber Ish says:

    How can I import repositories that I have on a different server from rc-2 that are under .scm/repositories?

  2. Rene Pfeuffer says:

    Currently there is no automated feature for this. To do it manually, you have some options:

    If you want to import all your settings from rc2 to rc4, you simply can copy the whole scm home folder.

    If you only want to copy the repositories into an _empty_ rc4 instance, you can copy the repositories folder and the file config/repository-paths.xml.

    If you want to “merge” the repositories from your rc2 instance with other repositories created in the rc4 instance, you have to copy the folders from the repository directory and manually merge the two config/repository-paths.xml files (this should not be hard to do).

    Finally you should check for absolute paths in the config/repository-paths.xml file. Normally all paths should look like repositories/9lRr86GMxR.

Leave a Reply

Your email address will not be published. Required fields are marked *

*