[
https://issues.apache.org/jira/browse/POOL-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660763#comment-16660763
]
Matt Benson commented on POOL-354:
----------------------------------
It looks like the original addition happened with
[https://github.com/apache/commons-dbcp/commit/377dd0a46189c53b9af1f89c7e4e9e1bc7698646]
. It would seem that fully hiding the test and dependencies in the associated
Maven profile would insulate downstream users from any surprises when building
the code.
> 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
> 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)
