[
https://issues.jboss.org/browse/WFLY-9855?page=com.atlassian.jira.plugin....
]
Tomaz Cerar commented on WFLY-9855:
-----------------------------------
[~dlofthouse] you are right about that. This kind of issues should be priority fixed for
anything that can be used outside of the server.
Client apps that might use such jar on classpath can be effected.
I am not sure if this exact jar is such that can be used on client.
I at the time of creation of this issue, I was analyzing all jars that are produced /
delivered in WildFly distro
[JDK9+] org.jboss.security.negotiation.spnego package is exported by
two jars
-----------------------------------------------------------------------------
Key: WFLY-9855
URL:
https://issues.jboss.org/browse/WFLY-9855
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Tomaz Cerar
Assignee: Tomas Hofman
Priority: Critical
Currently if you have
jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar
on your module path, jvm complains as both jars export package
org.jboss.security.negotiation.spnego
which violates the modules contract where only one module (jar) can provide single
package.
example error that jvm prints
{noformat}
Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package
org.jboss.security.negotiation.spnego to module wildfly.clustering.common
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)