Hi Gunnar,
Thanks for reporting the issue and working on this.
I have responded on the bug. Let us discuss on the bug.
Thanks & Regards,
Sarika
----- Original message -----
From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Sent by: jdt-dev-bounces@xxxxxxxxxxx
To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] [jdt-dev] Launching JUnit tests using argument file
Date: Tue, Aug 11, 2020 4:54 PM
Greetings,
I'm investigating an issue with launching JUnit tests in our code base after switching to JDK 11:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=565902
Launching JUnit tests started failing because the launch config arguments become too large for the OS to handle as command line arguments. I've implemented a simple shortener which will write the command line arguments into an argument file and use this one for launching. That solves the issue.
I appreciate any feedback on the patches if the proposed changes are acceptable or if a different solution is preferred. There are a few options and I'm happy to implement a different solution if desired.
FWIW, I'm also investigating why the argument list becomes so large. It looks like that Eclipse is collecting JDK specific options from the project classpath and combining it with all JVM specific options from the dependencies. In our case this leads to duplicate "--add-export" statements in the arguments list. I was wondering if the code should also be modified to wither avoid duplicate arguments on the command line or ignore JVM options from other projects in the dependencies. Any pointers are appreciated!
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
