Remove undeclared dependencies from Gradle build - #177
Conversation
These are a few dependencies that are missing and cause the build to fail when no network connection is available.
|
Thanks for digging into this — your diagnosis is right, and I traced where those five modules actually come from. Nothing in the project requests them. They are pulled in by Gradle's Groovy plugin: With a scratch
The catch with declaring them as
Since the modules are only needed by the Groovy compiler, the build can just say so and stop inferring. I pushed a commit to this branch that drops the five configurations {
groovyCompiler
nextflowRuntime
}
tasks.withType(GroovyCompile).configureEach {
groovyClasspath = configurations.groovyCompiler
}
dependencies {
groovyCompiler 'org.apache.groovy:groovy:4.0.31'
...
}Verified in a clean Could you confirm this builds in the Nix sandbox? Nothing undeclared should be requested now, so the packaging shouldn't need the extra dependencies at all. |
|
@pjones can you verify that my edits still work in your NixOS environment? |
|
@bentsherman Yes, your changes work in Nix build. Thank you! |
While creating a package for NixOS/nixpkgs I discovered a few undeclared dependencies. Builds using Nix happen in an isolated sandbox with no network connection. Without these dependencies the build would fail.
It's not clear to me why builds succeed for others. Perhaps these dependencies are cached or maybe just downloaded as needed. Either way I thought I'd open a PR.