Classpath too long on windows
See original GitHub issueI have a project with a very large number of dependencies, when we try to run pitest (using the gradle plugin) we get:
CreateProcess error=206, The filename or extension is too long
I tried resolving this by instead providing a fat jar with all the dependencies and the appropriate manifest Class-Path but no joy, i ended up getting:
No test library found on classpath. PIT requires either JUnit 4 (but can run JUnit 3 tests) or TestNG
Is there another work around to deal with the windows limit on command length?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
How to set a long Java classpath in Windows? - Stack Overflow
The Windows command line is very limiting in this regard. A workaround is to create a "pathing jar". This is a jar containing...
Read more >Mitigate long classpath on Windows for JavaExec #10114
Solution 2: Modify JavaExecHandleBuilder to always pass only the classpath as arg file (JDK 9+) · Pro · Con · Note.
Read more >Classpath too long… with Spring Boot and Gradle
Classpath too long … with Spring Boot and Gradle · Shorten the common path (as mentioned before). E.g. copy all your dependencies into...
Read more >Problem with running application - classpath too big - Old Forum
I get the following message at the command line in windows: The input line is too long. The syntax of the command is...
Read more >Windows version of tools.deps fails to launch Java if classpath ...
When the classpath needed to execute {{clojure}} gets sufficiently large on Windows, it can exceed the maximum size of a single command-line ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
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
@iwarapter It should be fixed in just released version 1.2.2 of the plugin. Just add
useClasspathFile = true
in your plugin configuration.Unless @iwarapter did not agree, this problem should have been already fixed for 3 years+ and that issue could be closed.