Sergej Koščejev
11/19/2024, 12:29 PM--include-build rather than programmatically?Vampire
11/19/2024, 12:40 PM-I from the commandline that can configure the necessary substitution.Sergej Koščejev
11/19/2024, 12:43 PMVampire
11/19/2024, 1:12 PMgradle.
You need gradle...settings... don't know from the top of my head. beforeSettings or afterSettings or settingsEvaluated or something like that.Sergej Koščejev
11/19/2024, 1:16 PMVampire
11/19/2024, 1:17 PMVampire
11/19/2024, 1:18 PMincludeBuild within the init script.Sergej Koščejev
11/19/2024, 1:22 PM--include-build option that I could use instead of the property. But since the build being integrated is not written nicely, it produces multiple artifacts and its name doesn't match the produced artifact so the default substitution heuristic of Gradle doesn't work. Okay, I thought, I could override that, but it turns out I can only do that within includeBuild in settings but not "if this build is included via --include-build then substitute those dependencies this way".
So I'll fall back to using the property anyway, I just thought that I could avoid it.Vampire
11/19/2024, 2:07 PMSergej Koščejev
11/19/2024, 2:07 PMVampire
11/19/2024, 2:08 PM--include-build is more for ad-hoc including or when you cannot or do not want to modify the including build.