Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17861

Providing Java-based SVN SCM provider

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • m2release-plugin
    • None

      It would be great if the M2Release plugin would use the configuration described in this http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin link, so as a result it will access SVN by SVNKit it turn (which is Java-based and auto-downloaded by MVN). Hence, this would be no need anymore to install SVN manually on all build slaves!

          [JENKINS-17861] Providing Java-based SVN SCM provider

          James Nord added a comment -

          The absolute last thing any plugin should do is change the behaviour of the build from what would be performed on the command line. If you want to use the pure Java provider you will need to configure it in your pom.

          James Nord added a comment - The absolute last thing any plugin should do is change the behaviour of the build from what would be performed on the command line. If you want to use the pure Java provider you will need to configure it in your pom.

            Unassigned Unassigned
            mkarg Markus KARG
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: