| Summary: | Virgo Web server v2.1 start failed when installed into a directory with a path containing white space | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | KwanKin Yau <alphax> |
| Component: | runtime | Assignee: | Violeta Georgieva <milesg78> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse.org, glyn.normington, milesg78 |
| Version: | 2.1.0.RELEASE | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
KwanKin Yau
Thanks for raising this. Hello, I tested the issue described above with the latest Virgo milestone release which is 3.0.0.M03. The issue is not reproducible. As there is a workaround i.e. extract Virgo distribution into a directory with a path that does not contain white spaces, I would prefer not to make changes in the old versions. Regards, Violeta FYI, this problem is back, at least as of version 3.0.5.RELEASE. I have the virgo distribution unzipped into the directory "~/test dir/" on my OS X machine; when I try to start virgo up, the console output is: test dir $ bin/startup.sh /Users/levineja/test dir/virgo-tomcat-server-3.0.2.RELEASE/bin/dmk.sh: line 21: cd: /Users/levineja/test: Not a directory /Users/levineja/test dir/virgo-tomcat-server-3.0.2.RELEASE/bin/dmk.sh: line 27: [: /Users/levineja/test: binary operator expected chmod: dir/virgo-tomcat-server-3.0.2.RELEASE/config/org.eclipse.virgo.kernel.jmxremote.access.properties: No such file or directory mkdir: /Users/levineja/test: File exists /Users/levineja/test dir/virgo-tomcat-server-3.0.2.RELEASE/bin/dmk.sh: line 168: cd: /Users/levineja/test: Not a directory Error: Exception thrown by the agent : java.lang.IllegalArgumentException: Expected word at end of line [test ] It's obviously not a *huge* issue, but it's probably worth addressing -- for me, it means that I have to have the distro in a place different than my regular workflow, which isn't a killer but is sure to get confusing here and there. Oh, and that was an unfortunate typo; I meant 3.0.2.RELEASE. Sorry about that. |