Henk van Voorthuijsen wrote:
>
>
>
> David Carson-2 wrote:
>>
>> I'm waiting on deploying an SVN server that will use svn 1.7 until
>> SvnKit has released its own full 1.7 support. This is because we use
>> several tools that themselves use SvnKit and these tools do not properly
>> handle the changes in 1.7.
>>
>
> We have successfully upgraded our repository to 1.7. As long as you keep
> your clients exclusively to 1.6, there should be no problem.
>
> But yes, a bit more current information on the download page would be
> appreciated.
>
> Henk van Voorthuijsen
>
There are reasons why this still might not be sufficient. We use Jenkins
and the Subversion plugin for Jenkins uses SVNKit. Even though the latest
Jenkins svn plugin was released yesterday, the Changelog is quiet on whether
or not the 1.3.7 version of SVNKit was integrated (so I assume it was not).
That means, Jenkins+svn still does not work with a 1.7 svn server, if "svn:"
protocol is required (as it is for me).
My guess is that the Jenkins svn plugin will not bother to integrate a new
SVNKit until 1.7 is available.
Thanks,
David
--
View this message in context:
http://old.nabble.com/will-latest-1.7-schedule-hold--tp33296760p33331342.html
Sent from the SVNKit - Users mailing list archive at Nabble.com.
