Oh going unpatched is really what is needed longer term... I had to give up trying to merge 1.3.6 and asked KK to do it in order to pull in some required fixes
On 14 February 2012 13:38, Christoph Kutzinski <[email protected]> wrote: > No other opinions on this? > > > -------- Original-Nachricht -------- >> Datum: Sun, 12 Feb 2012 17:21:50 +0100 >> Von: domi <[email protected]> >> An: [email protected] >> Betreff: Re: Using an unpatched SVNKit for the svn plugin? > >> +1 >> >> On 12.02.2012, at 11:44, Christoph Kutzinski wrote: >> >> > Hi, >> > >> > I've just seen that the Hudson guys are working on integrating SVNKit >> 1.3.7 and at the same time replacing the patched SVNKit with a vanilla one. >> > >> > http://java.net/projects/hudson/lists/dev/archive/2012-02/message/38 >> > >> > I think it would be a good idea to get inspired by this, as maintaining >> a patched SVNKit is - IMHO - not a good idea in the long run. >> > >> > >> > cheers >> > Christoph >>
