www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LEGAL-45) optional dependency on svnkit
Date Sun, 14 Jun 2015 02:00:07 GMT

     [ https://issues.apache.org/jira/browse/LEGAL-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henri Yandell closed LEGAL-45.
------------------------------
    Resolution: Not A Problem

Closing this. I think resolved.html now answers this with:

    https://www.apache.org/legal/resolved.html#optional

Namely that it can rely on svnkit if its use is optional, but it cannot include svnkit in
an Apache product by default. The user has to go get svnkit.

> optional dependency on svnkit
> -----------------------------
>
>                 Key: LEGAL-45
>                 URL: https://issues.apache.org/jira/browse/LEGAL-45
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>
> SVNKit is under a license that is somewhat similar to the GPL (it is almost identical
to the sleepycat license): http://svnkit.com/license.html
> It is unclear from the legal documentation on the status of *optional* modules. 
> Maven has developed an abstraction layer for various SCM systems, generally by running
their CLI tools. We would like to offer a provider that uses svnkit as an optional alternative
to the svn command line tools:
> http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnjava/
> The license of SVNKit doesn't affect our ability to distribute the provider under the
Apache License, but anyone distributing the SVNKit binary must also distribute their code
under an open source license.
> If we did this, we would keep the following:
> - it will not be made the default provider for SVN, that will remain the svn.exe based
version.
> - it will be an optional part of the build from source (through a Maven profile), and
will not be dependend on by other parts of the code
> - instructions on the site about how to use the svnkit provider would spell out that
it requires the external dependency and that it is under a more restrictive license
> - we don't bundle and distribute svnkit as part of our releases
> Note that there is a reasonable alternate home, but it would be a shame to move the code
out of Maven's oversight for this purpose alone.
> The discussion thread is here: http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200903.mbox/%3c9948cb690903181722s2431ec04nc6ea48e3cc2d1bc7@mail.gmail.com%3e
> Is this an acceptable use case?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message