Hi Brad,
I’m working with one of my students and we couldn’t get the embedded server to start. We ran --debug and it said it couldn’t find the jar c:\users\Admin which made us realize that her username had a space in it. It’s “Admin Parent”. Just an FYI. Any idea of a workaround or is that a bug that can be fixed? I can log it but wanted to ask here first.
Dan Card
Upgrade to the Bleeding edge. It’s fixed there in theory. Our switch to ProcessBuilder in 3.5 messed up the token splitting a wee bit.
Thanks!
~Brad
ColdBox/CommandBox Developer Advocate
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
Oh, here’s the ticket we had for it:
https://ortussolutions.atlassian.net/browse/COMMANDBOX-558
Thanks!
~Brad
ColdBox/CommandBox Developer Advocate
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
Hey Brad,
I think that solved some but not all of it. I got this --debug output from my student. I was going to post in the bug tracker, pushed what I thought was the right button then decided I’d play it safe and do it here. Didn’t want to do anything to your workflow. Sorry.
Dan
Hi Dan, it shouldn’t need solving at this point. The bug is fixed already (and the ticket resolved). Just download the bleeding edge build of CommandBox to test. Version 3.5.1-snapshot right now.
http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/3.5.1-snapshot/
Thanks!
~Brad
Ahh, sorry-- upon re-reading your message I see you were trying to say that you tried the new version and it still didn’t work. Looking at the debug output, the issue is the java agent. I just reproduced it locally. Let me push a fix for that.
Thanks!
~Brad
We did. I walked her through it on a goto meeting. I’ll ask her to do it again. It did get farther into the process though.
Dan, just an update on this-- I’m still trying to get it fixed. There’s something deep inside Runwar (the bit that starts server) that is not handling the space and I haven’t been able to track it down. I know this worked in the previous release, but we changed how we send JVM args to the background server process and it doesn’t handle the spaces. It’s not a matter of just needing to escape something-- it appears there’s some code breaking apart the command line tokens on spaces and not taking quotes into account.
Anyway, just in case you didn’t already know this you can always just work around the issue for now by setting up a custom server home for your coworker. Just create a commandbox.properties file in the same directory as the box.json and put someting like commandbox_home=C:\commandbox in it. It will stop using the user directory for the CommandBox home This is documented here:
https://ortus.gitbooks.io/commandbox-documentation/content/setup/installation.html
