Hi, I started the same work, see https://github.com/centic9/svnkit, in my fork there is a separate branch "incoming-1.8.x" which contains the pure 1.8.0. version, however I did a manual integration, so the svnkit-history is not visible, so yours is better...
According to the download-page of svnkit, the newer version will not work with 1.7 working copy any more, thus requiring all existing checkouts to be upgraded, I am not sure what tihs means to the plugin, if it should automatically upgrade working copies or should refuse to work on such working copy versions? Dominik. On Wednesday, November 27, 2013 5:09:45 PM UTC+1, jason.p...@acquitygroup.com wrote: > > 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.
