I took a stab at upgrading Jenkins SVNKit to merge in the recently released 1.8.0 SVNkit. Possibly even ok for a pull request. https://github.com/electrawn/svnkit
I then took a look at upgrading the Subversion plugin to handle the new SVNkit. It looks like pre 1.6 SVN working copies matched underlying SVN working copy format numbers. Then at 1.7 the number jumps inexplicably to 100 and there seem to be certain kludges to get working copies working with 1.7. What is the level of effort (LOE) to introduce 1.8 without breaking 1.7 functionality? This seems a bit more complex than altering one jelly file. *Jason Potkanski* Release Manager *ACQUITY GROUP * Part of Accenture Interactive -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
