-
Sub-task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
https://github.com/jboss/jboss-parent-pom/pull/160, https://github.com/jboss/jboss-common-beans/pull/34, https://github.com/jbosstm/jboss-transaction-spi/pull/38, https://github.com/wildfly/jboss-ejb3-ext-api/pull/8, https://github.com/jboss/openjdk-orb/pull/21, https://github.com/jbossas/jboss-vfs/pull/47
-
---
-
---
This might not get resolved (and it is not required for the main task) but I wanted to keep things in one place.
Since the plan is to rely on license names (provided in POMs) and only fall back to local config in cases where the license info is ambiguous we might as well fix the license names in dependencies maintained by JBoss. Some of these are old projects that might not see an update.
Currently the artifacts with missing/ambiguous licenses are:
- org.jboss:jboss-parent
- not a direct dependency but it is listed as "Public Domain" and JBoss artifacts that don't provide explicit license info default to this
- org.jboss:jboss-transaction-spi
- org.jboss:jboss-vfs
- org.jboss.common:jboss-common-beans
- org.jboss.ejb3:jboss-ejb3-ext-api
- org.jboss.openjdk-orb:openjdk-orb
- org.jboss.logging:jul-to-slf4j-stub
- this one actually has had the license name corrected but new version has not been released
- relates to
-
JBVFS-220 Provide unambiguous license name in POM
- Resolved