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 you like with jenkins, this would require a license
change, mostly GPL

This wouldn't apply if subversion is handled by another plugin, separated
from jenkins core distribution. Would be also a good opportunity to get rid
of those forks (during merge, I had to tweak the svnkit fork due to our for
on trilead-ssh !)

Maybe it's time for us to deprecate the subversion plugin. Not sure how to
handle backward compat, maybe core could keep a fake subversion plugin to
automatically install the (new) svn-plugin on first usage, like OSX Lion
does for java runtime

wdyt ?


2012/4/26 nicolas de loof <[email protected]>

> 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 <[email protected]>
>
>> What about having an other subversion plugin (not bundled with core
>> for license reason) called svn-1.7-plugin and which use svnkit 1.7 ?
>>
>>
>> 2012/4/26 Christoph Kutzinski <[email protected]>:
>> > 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 specific
>> patches to SVNKit are and how to apply them to SVNKit 1.7
>> >
>> > I'd like to take this opportunity to point out again that using a
>> patched library is *NOT* a good idea and we should try to see how the
>> Hudson guys solved it in this case.
>> >
>> >
>> > cheers
>> > Christoph
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>
>

Reply via email to