commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <>
Subject [jira] [Commented] (POOL-354) license problem with latest Apache commons-pool
Date Tue, 23 Oct 2018 14:49:00 GMT


Matt Benson commented on POOL-354:

It looks like the original addition happened with [] .
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:
>             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:
> 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
> Those deps only got added recently. The commit message is not really clear what it is

This message was sent by Atlassian JIRA

View raw message