[
https://issues.apache.org/jira/browse/FC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-297.
---
Resolution: Fixed
> [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.0.6
>
I have removed (and verified) the jboss jar dependency from fortress rest. The
repos are retagged. Artifacts rebuilt and staged once again. Let’s try this
again...
Hello,
This is an announcement to vote for the next release of Apache Directory
Fortress, 2.0.6.
Here are the list of bugs and
Shawn McKinney created FC-297:
-
Summary: [fortress-rest] Exclude jboss-rmi-api_1.0_spec-1.0.6
Key: FC-297
URL: https://issues.apache.org/jira/browse/FC-297
Project: FORTRESS
Issue Type:
> On Jul 6, 2021, at 10:12 AM, Emmanuel Lécharny wrote:
>
> This is irrelevant.
>
> Whatever due diligence CXF did, as soon as we know that there is a GPL/LGPL
> dependency, we can't cut a release with it in our packages.
>
> The simple fact it's a transitive dependency is not protecting us
> On Jul 5, 2021, at 1:18 PM, Stefan Seelmann wrote:
>
> I found one weird thing: the fortress-rest-2.0.6.war contains in
> WEB-INF/lib the jboss-rmi-api_1.0_spec-1.0.6.Final.jar.
That jar does not appear on a test machine using JDK 8.
Reading the ticket, it’s JDK 11 specific, which is what
