Intermediate output bin files contain full paths
See original GitHub issueTask org.jlleitschuh.gradle.ktlint.tasks.GenerateReportsTask
uses intermediate bin files with errors and these files contain absolute file paths that are problematic.
Because of this the task input changes depending on where the project is checked out. This causes cache misses.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
The intermediate directory (Debug\) contains files shared from ...
The cause of this problem is copying an intermediate directory that was created by Visual Studio, and that already contains files from a...
Read more >Inconsistent behaviour with Output Directory and Intermediate ...
Relative path for Intermediate Directory setting is relative to solution location. ... output\intermed" In VS2015 Output files go in "app/code/output/bin", ...
Read more >Output file path?
Currently there is no way to specify intermediate or output directories. The reason we use the structure build/$CONF/$TYPE/ and dist/$CONF/$ ...
Read more >Change the build output directory - Visual Studio (Windows)
Type in the path to generate output to (absolute or relative to the root project directory), or choose Browse to browse to that...
Read more >paths - Synopsys Detect - Black Duck Software
Scan Output Path ... The output directory for all signature scanner output files. If not set, the signature scanner output files will be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A cache relocateability test would be the best way. Here is an example (although outdated): https://github.com/gradle/kotlin-relocation-test
Here is such a relocation test inside the Android Cache fix plugin: https://github.com/gradle/android-cache-fix-gradle-plugin/blob/master/src/test/groovy/org/gradle/android/CrossVersionOutcomeAndRelocationTest.groovy
I’m more than happy to review a PR that resolves this issue. I don’t think that either @Tapchicoma nor I have time to tackle this at the moment.