Tad Fisher
Tad Fisher
@eyJhb Can you provide specific examples of dependencies that we don't resolve? I can add test cases for them.
The problem this project solves is that Gradle deals only in *dependencies*, when what we want is *artifacts*. Dependencies are generally Maven coordinates (group, module, version, and optionally classifier and...
Dependency verification metadata is *almost* what we want. However, the XML produced contains filenames of each artifact in the cache, which can be different from the filename in the external...
This is strange, I'm not sure why jackson is being pulled in at all. Let me investigate.
Does this work with the latest commit on `master`? That version of `jackson` is actually required by a plugin dependency.
Ah, once I run `nix-collect-garbage` to clear out my existing dependency derivations, I see this too. Investigating.
@mschwaig That's not really a viable solution; if `gradle2nix` generates bad hashes for itself then it will do so for any project you run it on, making it a non-usable...
Ah, that file is being served with CRLF (Windows) line separators, and Gradle is saving it to the cache with LF (Unix) line separators. I've moved hash generation to our...
This is the root cause, FWIW: https://github.com/gradle/gradle/issues/9072
@stites @mschwaig Try it now?