This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

x-posting a question I’d put up in dependency management.

so while using gradle 7.6 - when running

gradle init

on a multi-module maven project, and choose to opt into incubating features, it outputs the conventions plugin into

buildSrc

which seems to disagree with the release notes which state

When generating builds with the init task and opting in to incubating features, Gradle now places convention plugins under the build-logic directory instead of in buildSrc.

anyone else run into this? is it expected? documentation just missing the callout that it doesn’t apply to migrations?

This message was deleted.

This message was deleted.

:) https://twitter.com/gradle/status/1757839903839191133?t=G0vE3ZlMYUaiQihd2_3xdg&s=19

so, I've been working lately to create a Gradle platform&catalog from the SciJava pom, I have injected the generation in the pom.xml in this way but on the CI logs, I can see that Gradle is getting called at least 4 times, the last one failing with > [INFO] --- exec-maven-plugin3.2.0exec (generate-gradle-catalog-and-platform) @ pom-scijava --- > Error: Command execution failed. > java.io.IOException: Cannot run program "./gradlew" (in directory "/home/runner/work/pom-scijava/pom-scijava/target/gradle-scijava"): error=2, No such file or directory What am I doing wrong?

archived the channel