[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161894#comment-161894
]
Jamie Press commented on JENKINS-11381:
---------------------------------------
In JENKINS-11933, the 'duplicate' issue for this, someone added a patch file
that theoretically upgrades the svnkit version from the defective 1.3.6.1 to
the partially working 1.3.7 (this version can apparently speak to the 1.7.x
server, though not 1.7.x working copy).
As I would guess that most of us are only using Jenkins to check out the latest
version, this may serve as a workaround for many. However, applying a patch
file is a little beyond my expertise. Is anyone able to see if that patch
works, and if so, post the patched svnkit? It apparently makes a version called
1.3.7-jenkins-0.
All that being said, Dreyguy is right in saying the Hudson team made the right
move. Decoupling the svnkit from the plugin would be desirable.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
