From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

The code is pretty clean, nice work. I open an issue just to point out a common gotcha with the `TaskProvider` and `TaskContainer`.

hm, I really like the idea behind this, but the file sizes produced by it don't really seem to "scale" for the "commit to git" use case in a moderately sized project...

(that's a multi-module project with a decent amount of modules)

also, isn't this something that should be done on `assemble` rather than on `build` ? `build`  is `assemble`  + `test` IIRC

Thanks <@UBTK9PLRM> flagging the gotcha with looking up the `build` task.

<@U02FP3F38U9> thanks.  I've just switched the plugin over to `assemble`, seems like a good idea.

I've just merged <https://github.com/kronicle-tech/dependencies-file-gradle-plugin/pull/18> to reduce the file size of the `gradle-dependencies.yaml` files.  I've seen similar file size issues with a Micronaut codebase (one file was over 1MB...)

With the MR, this:

```  - name: "com.fasterxml.jackson.core:jackson-databind:2.13.3"
    moduleName: "jackson-databind"
    moduleGroup: "com.fasterxml.jackson.core"
    moduleVersion: "2.13.3"```
is replaced with this:

```  - name: "com.fasterxml.jackson.core:jackson-databind:2.13.3"
    direct: true```
Resolved dependencies are also no longer infinitely nested.  All resolved dependencies that have children are now all in the same top level list of resolved dependencies (per configuration).  So common transitive dependencies like BOMs that appear multiple times in a set of dependencies, should take up much less file space

Nice job! Dependency management is always a tricky one in JVM ecosystem.

At the same time what the plugin does seems a bit similar to the built-in feature of Gradle — <https://docs.gradle.org/current/userguide/dependency_locking.html#lock_state_location_and_format|dependency locking>. How do they compare (apart from the file format used)?

Hi Alex.  Great question.  Sorry I've not managed to reply sooner.  I've just written up a quick comparison on <https://github.com/kronicle-tech/dependencies-file-gradle-plugin/discussions/24>.  Feedback welcome!

Quick note, I believe that running `./gradlew dependencies --write-locks` on the root project will updates all dependency files in all subprojects.
So you shouldn’t need to `cd` into each of them