Hi,
If I can connect to thread.
@Koshuke
Have you checked pending pull requests on github for subversion-plugin.
Will those changes be included in 1.40 release with svn kit 1.7 ?
On Wed, May 9, 2012 at 2:52 PM, nicolas de loof nicolas.del...@gmail.comwrote:
On 04/26/2012 07:45 AM, nicolas de
On 04/26/2012 07:09 AM, Christoph Kutzinski wrote:
Hi,
in case no one else has mentioned, there are currently a lot of
complaints and a lively discussion in https://issues.jenkins-ci.org
/browse/JENKINS-11381 why Jenkins still doesn't support svn 1.7 now
that SVNKit 1.7 is released.
Indeed, I
On 26/04/12 15:45, nicolas de loof wrote:
Olivier explained me the licensing issue with svnkit 1.7, with
TmateSoft License is not compatible with Jenkins MIT as it requires
all derivative to follow complete source code for your application must
be available and freely redistributable under
Hi,
in case no one else has mentioned, there are currently a lot of complaints and
a lively discussion in https://issues.jenkins-ci.org/browse/JENKINS-11381 why
Jenkins still doesn't support svn 1.7 now that SVNKit 1.7 is released.
I would fix this myself, but I don't know what the Jenkins
Fully agree about patched libraries,
in the meantime, I've been inspired by the merge done by centic
on JENKINS-11933 and I'm finalizing a merge for svnkit 1.7.4 to our fork
2012/4/26 Olivier Lamy oliver.l...@gmail.com
What about having an other subversion plugin (not bundled with core
for
Olivier explained me the licensing issue with svnkit 1.7, with TmateSoft
License is not compatible with Jenkins MIT as it requires all derivative
to follow complete source code for your application must be available and
freely redistributable under reasonable conditions
MIT let you do whatever
