URGENT: Gradle build failures due to json-smart dependency

General
,
1

:warning: All A12 projects using UAA may be affected by this. :warning:

We are experiencing Gradle build failures for all supported A12 versions due to a dependency issue.
The root cause is that Spring defines a version range for the json-smart library, which leads to a build failure because the specified version is not available in our artifactories. This will cause the following error message:

FAILURE: Build failed with an exception.* What went wrong:
Execution failed for task ':server:app:compileJava'.
> Could not resolve all files for configuration ':server:app:compileClasspath'.
   > Could not find json-smart-2.3-SNAPSHOT.jar (net.minidev:json-smart:2.3-SNAPSHOT:20170326.024703-1).
     Searched in the following locations:
         <INTERNAL_LINK>
   > Could not find accessors-smart-1.2-SNAPSHOT.jar (net.minidev:accessors-smart:1.2-SNAPSHOT:20170326.024649-2).
     Searched in the following locations:
         <INTERNAL_LINK> Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Quick Fix: Delete the ~/.gradle/caches folder in your user directory. This will resolve the issue of loading the incorrect json-smart version.

The UAA team has released 8.1.2 (2024.06-ext3) and 7.5.7 (2023.06-ext10) to fix this by forcing the json-smart version to 2.4.10.

If you have any questions or concerns, feel free to reach out.

2

We saw this failure also on a TPI Jenkins. How should this be handled?

EDIT: I was just informed that the problem was solved in our TPI Jenkins without us needing to do anything. Not sure what solved the issue.

3

Heyho,

We forced the non-Snapshot versions

implementation("net.minidev:accessors-smart:1.2")
implementation("net.minidev:json-smart:2.3")

We had no problems with it

4

Moin @andreas-fresh-mesa, @tjorben-atomic-moss

UAA forces the json-smart version to 2.4.10, and this is included in either UAA 8.1.2 (2024.06-ext3) and UAA 7.5.7 (2023.06-ext10) as patches.

This way it is also not necessary anymore to provide project-side workarounds by forcing the version, so as soon as you update to one of these UAA versions, you can remove the workaround.