-
Notifications
You must be signed in to change notification settings - Fork 40.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning in build about json dependencies #29387
Comments
Thanks, Dave. We have dependencies on
In each case, it's a transitive dependency of Of the above modules, the following also have a dependency on
None of these will affect users as they're all on the test compile or test runtime classpath. We also have a dependency on I think we should try to avoid the duplicate JSON classes when the starters are combined. However, that's easier said than done as |
I wonder if I would raise an issue with them, but they use JIRA and it won't let me log in currently. |
Thanks for the heads up! @absurdfarce this could be indeed added to your current work on apache/cassandra-java-driver#1580. If The reason why this transitive dependency is still showing up is here: apache/cassandra-java-driver@ca8de6a. |
I can confirm that the changes in apache/cassandra-java-driver#1580 cause org.json:json to be marked as an optional dependency as well. When we made Esri an optional dependency the transitive deps it brought along with it were also marked as optional... and that's how org.json:json gets into the core and shaded JAR deps. |
This has been fixed in 2.7 by the Cassandra 4.14 upgrade. I don't think we risk destabilising things by doing anything in 2.6.x. |
I think that
spring-boot-actuator-autoconfigure
(tests) depend oncom.datastax.oss:java-driver-core
brings in a whole mess of things includingorg.json:json:20090211
com.vaadin.external.google:android-json
directlyPossibly some pruning of the datastax dependency would help.
The text was updated successfully, but these errors were encountered: