Support for projects unlinked from root

[blast-hardcheese]

For some time, I was wondering why only some libraries on https://github.com/twilio/guardrail/ were receiving library update PRs.

After digging in a bit, running stewardDependencies locally, I discovered that due to stewardDependencies collecting libraryDependencies from the project it was launched in, if there were any projects that were only accessible fully qualified, they'd be completely left out of analysis.

To put it differently,

sbt> stewardDependencies // Only lists a couple dependencies, defined on `root`
sbt> sampleAkkaHttp/stewardDependencies // Finds dependencies that need to be updated

The reason for this is surely due to my lack of how to properly structure an SBT project to serve my needs, but the guardrail integration tests are run in subprojects that are only able to be compiled during integration tests, as all other times the required source files have not been generated yet.

I was able to play a little shell game with my dependencies, which works pretty decently: guardrail-dev/guardrail#664

... though I wonder if there's not a more elegant solution for this problem, perhaps .steward.conf containing projects = foo, bar, baz or similar.

This seems somewhat related to #1158 as well, though that issue seems to be with multiple, separate invocation roots, whereas mine is just separate command prefixes plus an aggregation phase.

As always, thank you for this excellent tool, and have a fantastic day writing Scala!

[fthomas]

You're right that Scala Steward only updates dependencies that are listed by libraryDependencies of the root project. Running that task in the root project will only run it in subprojects that are aggregated by the root project. I'm not aware of a way to list dependencies for all subprojects regardless whether they are aggregated by the root project or not. If it exists I'm open to discussing if Scala Steward should be changed in this direction.

I also think that guardrail-dev/guardrail#664 looks like a good workaround when you don't want certain subprojects aggregated in the root project but still want to benefit from Scala Steward's automatic updates. The good thing about this solution is that library definitions are still only in the sbt build and do not need to be duplicated in some Scala Steward specific config file.

[eugeniyk]

@blast-hardcheese what we endup with giter8 templates (same - empty root dependencies, but lot's inside) is to regenerate dependencies.gen.sbt inside root that will aggregate them (simple bash scripts ;)

Then Scala steward update in both places - root (gen) and under

[exoego]

IIUC, this is covered by repo-specific config

buildRoots = [ ".", "subfolder/projectA" ]

which was introduced in #1875
So let me close as resolved.
See https://github.com/scala-steward-org/scala-steward/blob/main/docs/repo-specific-configuration.md for config detail.