You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it does give the report like this, but it would be nice to further enhance how many subprojects it has scanned, related to each subproject, what are the upgrades needed along with this summary that it gives currently.
When you apply this plugin to a project it will aggregate itself and the child projects into a report. This generally means you apply it to the root project, the : in the title above. If you apply it to subprojects then you will also see reports like :app, :library, :a:b:c. As most multi-project builds use only 2-level trees, you would get the individual subproject reports scoped to just themselves and an aggregate.
This typically isn't desirable because managing dependencies that diverge across subprojects is annoying. Instead maintaining a centralized manifest, like a bom or version catalog, lets you update a single location and have consistent versions.
Currently, it does give the report like this, but it would be nice to further enhance how many subprojects it has scanned, related to each subproject, what are the upgrades needed along with this summary that it gives currently.
The text was updated successfully, but these errors were encountered: