jvmArgs comma separation breaks for certain JVM arguments
See original GitHub issueGiven PIT 1.4.2 (and quite likely other versions as well) it is impossible to pass any JVM arguments that themselves have comma separation. Such an example is -XX:CompileCommand=command,method[,option]
In our case it’s necessary to affect how JIT is performed and thus it doesn’t work.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to set JVM arguments in IntelliJ IDEA? - Stack Overflow
Intellij allows you to specify two types of arguments when running a Java program: VM Options. Enables you to modify attributes of the...
Read more >Include the Java agent with a JVM argument
This document describes how to pass the -javaagent argument to the JVM for your framework. This installation step ensures the agent is included...
Read more >Kubernetes: Wrongly parsing JVM arguments when using ...
jvm -arguments) is splitting the value by comma. The problem is that some values need to keep the comma characters, for example, using:...
Read more >The java Command - Oracle Help Center
The content of the JDK_JAVA_OPTIONS environment variable is a list of arguments separated by white-space characters (as determined by isspace() ). These are ......
Read more >Specify JVM Options - Pants
You need to specify command-line options for the JVM when running a Scala or ... options can also be separated by line (just...
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
One option could be to just merge them all to a single list.
I’ll do that. It is going to take a few days, but I am interested. 😃
That was the idea, but it was a stupid one as you are quite correct, we could just have a param without the
.withValuesSeparatedBy
call.Guess the only question is how it should behave if both parameters are supplied.
If you’ve got time to put a pull request together and think about it, that would be great.