Jonathing
05/10/2025, 6:48 PMsettings.gradle
, at-gradle/build.gradle
, and at-gradle/settings.gradle
. It also includes the log with the failure of task :at-gradle:assemble
. https://gist.github.com/Jonathing/9c299e883cb83993c25b80b66d81e9e0
The only thing I could think of is maybe it doesn't like that I'm trying to use the root project as an included build instead of a sub project? Thanks in advance to anyone who can give pointers on what's going on.
EDIT: Figured it out. Basically it doesn't like if I try to include the rootProject as a build from a subproject that's also an included build. So my compromise was to make an empty root project that includes two builds, where one has the dependency substitution.Vampire
05/11/2025, 10:34 AMVampire
05/11/2025, 10:37 AMVampire
05/11/2025, 10:41 AMVampire
05/11/2025, 10:46 AMincludeBuild
a project with Gradle plugins, you should do so from within pluginManagement
.
And by defining trivial version catalogs in the settings script instead of a TOML file, you give away one of the biggest advantages of version catalogs. If you now change any version, the settings script changes and thus the classpath of every task changes and thus all tasks are out-of-date. If you use a TOML, then only the tasks actually affected will be out of date.Jonathing
05/11/2025, 1:21 PMJonathing
05/11/2025, 1:22 PMJonathing
05/11/2025, 1:26 PM