|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
[JIRA] (JENKINS-13790) Subversion externals fail
tom.pal...@whiteonesugar.com (JIRA) Fri, 28 Dec 2012 07:07:57 -0800
- [JIRA] (JENKINS-13790) Subversion ext... dsear...@siginnovations.com (JIRA)
- [JIRA] (JENKINS-13790) Subversio... alek...@java.net (JIRA)
- [JIRA] (JENKINS-13790) Subversio... n.vancauwenber...@televic.com (JIRA)
- [JIRA] (JENKINS-13790) Subversio... li...@gmx.li (JIRA)
- [JIRA] (JENKINS-13790) Subversio... tom.pal...@whiteonesugar.com (JIRA)
- [JIRA] (JENKINS-13790) Subversio... gmy...@siginnovations.com (JIRA)
- [JIRA] (JENKINS-13790) Subversio... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13790) Subversio... scm_issue_l...@java.net (JIRA)
I have a fix for this within my fork of the plugin on github. It uses the native support within SVNKit to determine the URLs for the svn:externals that the project contains. Because it natively hooks into SVNKit it works regardless of the SVN version you wish to use in your working copies. The pull request is https://github.com/jenkinsci/subversion-plugin/pull/30.