Tad Fisher

This issue is caused by me; when I hack on gradle2nix, it's pulling hashes from my local gradle cache, which normalizes certain artifacts such as POM files. It's time to...

Packaging gradle2nix should be fine, so I would start with that. I sort of disagree with integrating the `buildGradle` function in nixpkgs. We don't do that for node2nix, for example,...

One incompatible change I want to make is to switch to SRI hashes, so I will likely rename the `sha256` field for dependency objects.

Maven BOM artifacts are currently supported via the built-in Gradle `platform()` and `enforcedPlatform()` APIs. Projects generated using that tool do not use Gradle's BOM support; instead they apply the [Spring...

I've integrated Nix into my Android app build in a more straightforward way, as gradle2nix isn't geared toward usage in a project, but more toward packaging third-party projects. Here's a...

@eyJhb There are a few reasons that combine to force us to do this: - Gradle resolves artifacts independently for each of these scopes, using a potentially different set of...

Thanks, I'll take a look.

ZAP contains plugins in its `buildSrc` project, which are those dependencies with coordinates `unspecified:unspecified:unspecified`. That's fine, but the transitive dependencies are coming through with no version information. I'm going to...

@pstn I'm fairly confident that is the Android Databinding code failing to locate the Android SDK, which is an impurity in the build. I've been meaning to get gradle2nix working...

Is this your own project, as in you control the source? Because I would suggest improving the Gradle build instead so you can build the project in one run. Looking...