[ 
https://issues.apache.org/jira/browse/POOL-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660792#comment-16660792
 ] 

Mark Struberg commented on POOL-354:
------------------------------------

Gary, I assigned it to you. You applied the patch and probably have more 
background info about what to do.
Afaict we have 2 options
a.) make those classes optional and move the deps to a profile
b.) switch to Apache geronimo-transaction TxMgr.

> license problem with latest Apache commons-pool
> -----------------------------------------------
>
>                 Key: POOL-354
>                 URL: https://issues.apache.org/jira/browse/POOL-354
>             Project: Commons Pool
>          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)

Reply via email to