[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161716#comment-161716
]
Qin Ding edited comment on JENKINS-11381 at 4/18/12 10:14 AM:
--------------------------------------------------------------
There is my workaround :
1. Install the latest CollabNet Subversion Client to the server, which provides
svn command-line tool.
2. Put all maven commands into a shell, i.e. bat for Windows.
3. Use maven-antrun-plugin to execute that shell.
4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and
options'.
It works because the shell will use the system variable where PATH includes the
latest CollabNet path rather than the old svn path used by Jenkins.
My website describes more :
http://www.softhinker.com/in-the-news/howtomakejenkinssupportsubversion17
was (Author: softhinker):
There is my workaround :
1. Install the latest CollabNet Subversion Client to the server, which provides
svn command-line tool.
2. Put all maven commands into a shell, i.e. bat for Windows.
3. Use maven-antrun-plugin to execute that shell.
4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and
options'.
It works because the shell will use the system variable where PATH includes the
latest CollabNet path rather than the old svn path used by Jenkins.
My website : http://softhinker.com
> 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
