New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NETBEANS-3254 Remove allowAmbiguousCommands flag #1849
Conversation
Removes the jdk.lang.Process.allowAmbiguousCommands flag netbeans.conf. Instead defines a NETBEANS_MAVEN_COMMAND_LINE environment variable local to the ProcessBuilder used to launch Maven, and pass a reference to that variable on the cmd.exe command line. With that change, the quote prefixing and suffixing of the Maven command line prevented the command line from being properly launched so it was removed. (Tested both with the embedded Maven 3.3.9 and an external Maven 3.6.3)
Hi @lhochet, how to test that ? |
Hello @ebarboni,
|
works, allowAmbiguousCommands is only for this maven execution ? |
@ebarboni it was certainly only added late in 11.2 because of reports of this bug with Maven on the JDK updates that had just been released. I don't know whether other things might be affected though - Maven was very obvious - but IDE wasn't tested without that option for very long! Nice fix btw! |
@neilcsmith-net thanks for comment. |
…e as it could be of use for non Maven contexts
@ebarboni sure, done. It could still be of use to external processes (.bat/.cmd particularly) being launched from NetBeans and having double quote(s) within double quoted arguments. |
maybe we should remove just after 11.3 release to see on longer period |
@ebarboni that would be good and NetCAT for 12.0 should hopefully catch any other issues. |
Removes the jdk.lang.Process.allowAmbiguousCommands flag from netbeans.conf.
Instead defines a NETBEANS_MAVEN_COMMAND_LINE environment variable
local to the ProcessBuilder used to launch Maven, and pass a reference to that
variable on the cmd.exe command line.
With that change, the quote prefixing and suffixing of the Maven command
line prevented the command line from being properly launched so it was removed.
(Tested both with the embedded Maven 3.3.9 and an external Maven 3.6.3)