[
https://issues.apache.org/jira/browse/CLEREZZA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632374#comment-14632374
]
Minto van der Sluis commented on CLEREZZA-944:
----------------------------------------------
Unfortunately it has not yet been fixed.
The original OpenLink JDBC drivers (version 4.0 and 4.1) are included into sort
of a custom maven repo. From there the binary dependency is used to wrap it
into a OSGI bundle.
So actually it's a bit of a slippery area. So it might be safer to move this
stuff out of Clerezza into something like contrib.
> Virtuoso JDBC legal aspect
> --------------------------
>
> Key: CLEREZZA-944
> URL: https://issues.apache.org/jira/browse/CLEREZZA-944
> Project: Clerezza
> Issue Type: Bug
> Reporter: Reto Gmür
> Priority: Critical
>
> The issue is discussed in LEGAL-173.
> Despite that issue not being closed so far we have by now releases
> org.apache.clerezza:ext.virtuoso.jdbc which includes the jar under the GPL2
> with special exception license.
> Th special clause allows "to use the unmodified client libraries" in non GPL
> software. However it also says that "In all other respects you must abide by
> the terms of the GPL", I think this means at least that the notice file
> should provide the note that there is no warranty.
> Also if the virtjdbc license qualifies as category B the following applies:
> "Although the source must not be included in Apache products, the NOTICE
> file, which is required to be included in each ASF distribution, must point
> to the source form of the included binary (more on that in the forthcoming
> "Receiving and Releasing Contributions" document)." (from
> http://www.apache.org/legal/3party.html)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
