Jeffrey Holt

After my tests with jdk 23, I think there is a java for windows bug that manifests only when JNI_CreateJavaVM starts the JVM. I don't see a problem when the java command starts the JVM. I think the java command main is handling the bounding characters correctly. I think a reasonable workaround for the bug is to strip bounding characters (if they're used) before calling JNI_CreateJavaVM in jnihead.c. I also looked in the "git log -p" output that extends all the way back to 2006. I see no reference...

After my tests with jdk 23, I think there is a java for windows bug that manifests only when JNI_CreateJavaVM is how a JVM is started. I don't see a problem when the java command starts the JVM. I think the java command main is handling the bounding characters correctly. I think a reasonable workaround for the bug is to strip bounding characters (if they're used) before calling JNI_CreateJavaVM in jnihead.c. I also looked in the "git log -p" output that extends all the way back to 2006. I see no...

After my tests with jdk 23, I think there is a java for windows bug that manifests only when JNI_CreateJavaVM is how a JVM is started. I don't see a problem when the java command starts the JVM. I think the java command main is handling the bounding characters correctly. I think a reasonable workaround for the bug is to strip bounding characters (if they're used) before calling JNI_CreateJavaVM in jnihead.c.

After my tests, I think there is a java for windows bug that manifests only when JNI_CreateJavaVM is how a JVM is started. I don't see a problem when the java command starts the JVM. I think the java command main is handling the bounding characters correctly. I think a reasonable workaround for the bug is to strip bounding characters (if they're used) before calling JNI_CreateJavaVM in jnihead.c.

After my tests, I think there is a java for windows bug that manifests only when JNI_CreateJavaVM. I think a reasonable workaround for the bug is to strip bounding characters (if they're used) before calling JNI_CreateJavaVM in jnihead.c.

Ticket 232 (JAVA_TOOLS_OPTIONS bug) was not properly fixed nor was it closed

With version 3.50, I have no problem if apostrophes are used but I do have a problem when quotes are used. Of course, neither apostrophes nor quotes are necessary but some people don't care. This works in 3.50 set JAVA_TOOL_OPTIONS='something in the way' This also works in 3.50 but it's DOS insanity set JAVA_TOOL_OPTIONS=something in the way This does not work in 3.50 set JAVA_TOOL_OPTIONS="something in the way"

With version 3.50, I have no problem if apostrophes are used but I do have a problem when quotes are used. Of course, neither apostrophes nor quotes are necessary but some people don't care. These work in 3.50 set JAVA_TOOL_OPTIONS='something in the way' This also works in 3.50 but it's DOS insanity set JAVA_TOOL_OPTIONS=something in the way This does not work in 3.50 set JAVA_TOOL_OPTIONS="something in the way"