You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/10/23 15:23:00 UTC

[jira] [Updated] (DBCP-525) license problem with latest Apache commons-dbcp

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

Mark Struberg updated DBCP-525:
-------------------------------
    Summary: license problem with latest Apache commons-dbcp  (was: license problem with latest Apache commons-pool)

> license problem with latest Apache commons-dbcp
> -----------------------------------------------
>
>                 Key: DBCP-525
>                 URL: https://issues.apache.org/jira/browse/DBCP-525
>             Project: Commons DBCP
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Mark Struberg
>            Assignee: Gary Gregory
>            Priority: Blocker
>
> our pom includes various JBoss artifacts.
> * jboss-parent license 'Public Domain' without any further clarification. Would need a clarification imo.
> * org.jboss.narayana.jta:narayana-jta LGPL
> * org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec LGPL
> * org.jboss:jboss-transaction-spi LGPL
> * org.jboss.logging:jboss-logging LGPL
> According to the following LEGAL ticket those dependencies should imo not be there as they are required in the build:
> https://issues.apache.org/jira/browse/LEGAL-207
> My interpretation is that having LGPL dependencies are oki-ish as long as they are purely optional. E.g. if they are only in an optional profile in the build and implement some public api.
> Those deps only got added recently. The commit message is not really clear what it is about. 
> https://github.com/apache/commons-dbcp/commit/5660855731502d00319f54cd584c95afa487a854



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)