Gradle multi-module, Windows 10 & KTEs lock shared jars
See original GitHub issueThere’s a combination we use of Windows, Gradle (latest version) and precompileJte (now KTE), which caused shared built jars to be “locked” so a gradle clean won’t work.
This problem didn’t happen with JTEs and plugin & library version 1.8, but happens now with KTEs & plugin & library version 1.9.
Could it be a file/resource opening and you’re not closing it perhaps?
I can do a gradle clean on the compileKotlin
task for instance, but as soon as I do precompileJte
then this problem happens so I’m fairly sure there’s an issue somewhere in the jte kotlin module.
I tried it all on Ubuntu and it seems fine.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Learning the Basics - Gradle User Manual
In most cases, a project relies on reusable functionality in the form of libraries or is broken up into individual components to compose...
Read more >Gradle multiple jars from single source folder - Stack Overflow
The advantage of this solution is that we make a proper Gradle multi module project with correct dependencies, not just tasks for building...
Read more >Gradle daemons lock KSP-related JAR files on Windows #1040
I use KSP in a multi-platform multi-module project with Idea CE. (But currently KSP is applied only on one JVM project.)
Read more >Using Gradle and the App Engine Plugin - Java 8
This page explains how to use Gradle with an App Engine project in the standard ... repositories { // repositories for Jar's you...
Read more >Gradle multi project build — substituting jar dependencies ...
One of the projects we're working on recently is using a multi-module architecture. Each feature module is kept in a separate Git repository ......
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
I just pushed
System.setProperty("kotlin.environment.keepalive", "false");
to the gradle and maven compiler. I think mvnd will have the same problem on windows.Glad you got it working! I’m gonna close this issue, feel free to reopen if there’s something still missing 👍
The
kotlin.environment.keepalive=false
seems to work as well.Perhaps this should be the responsibility of the plugin?
Thanks for tracking down the solution 😃