-
Bug
-
Resolution: Done
-
Major
-
7.4.3.GA
-
False
-
None
-
False
-
-
-
-
-
-
-
It has been reported jars transitively reachable from wildfly-cli are not contained within the maven repo:
Transitive dependencies from "wildfly-cli" the following three could not be resolved:
>Could not find org.wildfly.security:wildfly-elytron-http-oidc:1.15.9.Final-redhat-00001. > Could not find org.wildfly.security:wildfly-elytron-jose-jwk:1.15.9.Final-redhat-00001. > Could not find org.wildfly.security:wildfly-elytron-jose-util:1.15.9.Final-redhat-00001.
-------------------------------
bmaxwell Update 2022-08-25:
Clarification of the use case , issue and proposed solution.
Use case: standalone application that will use the Java Management API, as per [0] you would use the jboss-cli-client.jar on your classpath.
Issue: the maven dependency org.wildfly.core:wildfly-cli contains [1] & [2] which is the private module jar used in EAP and the jboss-cli-client.jar. Users should not be using the wildfly-cli.jar and if you use wildfly-cli-client.jar (jboss-cli-client.jar) it is self sufficient, it has no dependencies.
Proposed Solution: Move wildfly-cli-client.jar to org.jboss.eap:wildfly-cli-client this would:
- separate the wildfly-cli & wildfly-cli-client (jboss-cli-client) jars
- allow wildfly-cli-client to stand by itself, ie it has no dependencies, so depending on it would not try to pull down transitive dependencies that are not required
- being under org.jboss.eap makes more sense, because this is where jboss-client.jar is located in org.jboss.eap:wildfly-client-all
- being under org.jboss.eap , would also have it versioned with the EAP version such as 7.4.6 , which makes more sense when a CP is released, you can just update the version to this, as opposed to where it is now, it is versioned with the WF Core version (and WF Core is a sub component effectively of EAP and not a version that the user should have to keep track of)
------------------------------------
[1] https://maven.repository.redhat.com/ga/org/wildfly/core/wildfly-cli/15.0.15.Final-redhat-00001/wildfly-cli-15.0.15.Final-redhat-00001.jar - this is the EAP Private Module: $JBOSS_HOME/modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-15.0.15.Final-redhat-00001.jar
[2] https://maven.repository.redhat.com/ga/org/wildfly/core/wildfly-cli/15.0.15.Final-redhat-00001/wildfly-cli-15.0.15.Final-redhat-00001-client.jar - this is $JBOSS_HOME/bin/client/jboss-cli-client.jar
------------------------------------
[3] https://maven.repository.redhat.com/ga/org/jboss/eap/wildfly-client-all/7.4.6.GA-redhat-00002/wildfly-client-all-7.4.6.GA-redhat-00002.jar - this is $JBOSS_HOME/bin/client/jboss-client.jar
- incorporates
-
WFCORE-6038 The org.wildfly.core:wildfly-cli:client artifact has unneeded dependencies
- Closed
- is incorporated by
-
JBEAP-24167 (7.4.z) Upgrade WildFly Core from 15.0.19.Final-redhat-00001 to 15.0.21.Final-redhat-00002
- Closed
- is related to
-
JBEAP-23942 [GSS](7.4.z) wildfly-cli-client.jar should be in org.jboss.eap:wildfly-cli-client instead of org.wildfly.core:wildfly-cli
- Closed
- links to