nebula-plugins / nebula-plugins/nebula-clojure-plugin
[BUG]On Windows destinationDir will be null
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 19
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
This problem does not occur on Mac and Linux.
gradle version: 8.13
My temporary solution is to add the following configuration in build.gradle.kts
tasks.withType<nebula.plugin.clojuresque.tasks.ClojureCompile>().configureEach { destinationDir = file("$buildDir/classes/java/main") }
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the build.gradle.kts workaround and the ClojureCompile task configuration, then reproduce the Gradle 8.13 build on Windows and compare it with Mac/Linux behavior. Done means the task receives a valid destinationDir without a project-level workaround; the issue names no source file or test, so locating coverage is part of the investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, groovy
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100