Plugin id for old fashioned plugin declaration still seems to be not updated to v2

[nuhkoca]

Hello @mannodermaus,

Congratulations on the v2 release and I’m excited to try it out. However, I am getting couple of issues:

• I did notice a small nuance between the new plugin ID and the legacy one, though. It looks like de.mannodermaus.gradle.plugins:android-junit5 is still required when using the old-style plugin declaration (for example, adding it as a dependency in build-logic). I tried using de.mannodermaus.gradle.plugins:android-junit, but that fails.
• And one dependency cannot be found

Could not find de.mannodermaus.junit5:core:2.0.0.
 Searched in the following locations:
 - https://dl.google.com/dl/android/maven2/de/mannodermaus/junit5/core/2.0.0/core-2.0.0.pom
 - https://repo.maven.apache.org/maven2/de/mannodermaus/junit5/core/2.0.0/core-2.0.0.pom

Are you aware of this, and is it something you’re planning to address?

[bddckr]

The new plugin ID seems to be de.mannodermaus.android-junit:de.mannodermaus.android-junit.gradle.plugin. I normally find these by googling for the exact string, in this case "de.mannodermaus.android-junit" and heading to the search result on Maven Central: https://central.sonatype.com/namespace/de.mannodermaus.android-junit Click through to get that latest full dependency name to apply in convention plugins!

(This new full dependency name seems to be following the stock Gradle plugins convention. When that convention is followed, it's something:something.gradle.plugin. I believe there's a Gradle plugin everyone uses these days to configure their plugin, using that convention that way.)

[nuhkoca]

Somehow I can't migrate from 1.14.0.0 to 2.0.0 yet. Even if I do not explicitly use de.mannodermaus.junit5:core but I am getting

Could not find de.mannodermaus.junit5:core:2.0.0.

[bddckr]

That didn't change. Only the plugin changed. The core dependency is still at de.mannodermaus.junit5:android-test-core. At least as far as I can see, that is!

[mannodermaus]

@bddckr is correct, only the plugin ID has been updated. That said, if you're experiencing a failure during sync related to a core artifact, something might be off about the packaging, as it's supposed to be android-test-core. I'll take a look shortly!

[nuhkoca]

Okay, I think I found the culprit. It was because of that dependency in one of our gradle modules

testImplementation(libs.compose.material)

And it caused project to failing. I checked and I don't need it. Thanks for swift turnarounds. I am closing the issue.

[jrgonzalezg]

There seems to be some transitive dependencies on that wrong de.mannodermaus.junit5:core:2.0.0 artifact. In my case the dependency resolution shows this failure:

+--- de.mannodermaus.junit5:android-test-compose-junit6:2.0.0
| +--- org.junit:junit-bom:6.0.1 (*)
| +--- de.mannodermaus.junit5:core:2.0.0 FAILED

So it seems at least in some cases the android-test-compose-junit6 dependency gets added and that depends on the wrong artifact. Maybe that is not added if some compose libraries are also not added but it is probably failing depending on what other (Compose) libraries are added on a project?

[mannodermaus]

Yeah, that transitive dependency is supposed to be android-test-core-junit6 instead. I'll reopen this and address the change in the POM shortly.

[jrgonzalezg]

I tried to search for this in the code to make a PR myself but I don't really follow where that transitive dependencies are defined. Could you give me some clues on where the changes are needed if you don't have time for making a PR for a fixed release right now?

[mannodermaus]

Turns out the POM was correct all along, but the module metadata did not get the same treatment. Resolved in 2.0.1

[jrgonzalezg]

Thanks!, that did not look easy! :-D. It is working fine now 😄