Skip to content

Conversation

@patrick-dedication
Copy link
Contributor

@patrick-dedication patrick-dedication commented Dec 1, 2024

As noted here I would like to add publishing for the gradle module metadata.

But first I need to get a hang of the setup and maybe even simplify stuff.
Here is a first simplification, the commit descriptions should explain why this is ok, otherwise feel free to ask.
For testCompile see here and here

* using testCompile has been discouraged since Gradle 3.4
* made sure dependencies on all other configurations are unchanged
* no need to change it to testImplementation since testCompileClasspath
  and testRuntimeClasspath extend from implementation
* compileClasspath already extends from implementation
@patrick-dedication patrick-dedication requested a review from a team December 1, 2024 12:35
@jjohannes
Copy link

@patrick-dedication asked me to have a look at this. The change looks correct to me as the testCompile scope no longer exist in Gradle 8.x. The reason the code was not failing is because in this super compact Groovy notation, Configurations (scopes) that do not yet exists are created on demand. So the code right now creates an empty Configuration called testCompile that is never used.

Extending compileOnly is not necessary as Patrick explained in the commit message.

@eddumelendez eddumelendez changed the title Simplify shading configuration setup Don't extend configuration compileOnly and testCompile from shaded Feb 18, 2025
@eddumelendez eddumelendez merged commit 2fa7f65 into testcontainers:main Feb 18, 2025
108 checks passed
@eddumelendez eddumelendez added this to the next milestone Feb 18, 2025
@eddumelendez
Copy link
Member

Thanks for your contribution, @patrick-dedication! and for your comments on @jjohannes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants