OK, I’ve got something I’d like to contribute, I’m just wondering how to go about it now…
It would be extremely useful if there were a mode I could put normal gradle2nix builds in where I could set __sandbox = false; and the plugin would run through the tasks I specify in the derivation as if I were running the gradle2nix command. Full internet connectivity and so on, but the lockfile can also be a build artifact.
I’m hoping to run something like that in CI. If one of our developers makes a change that touches dependencies and sets the correct option on their test build, it will generate the lockfile for them, automating a bunch of toil.
This looks great although unfortunately doesn’t quite work for the gradle package I’m trying to build. It has a custom ivy repository and it doesn’t find the artifact, even if I specifically build the subpackage that references it and it gets included in the gradle.lock file. I guess I could try to create a simple test to replicate this if that’s any help.