Bug #180
Startup script is bash-specific and won't run on Windows without Cygwin
| Status: | Closed | Start: | 12/03/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Rémy-Christophe Schermesser | % Done: | 100% |
|
| Category: | Core | |||
| Target version: | 1.2.0 | |||
| Problem in version: |
Description
As discussed in issue #174, the bin/lsc script is written in bash, and therefore doesn't run on Windows. I'm opening this issue to track this problem.
Attached to this message is a proposed alternative for bin/lsc in the form of a BAT script for Windows. Rémy will be testing it (thanks!).
Associated revisions
Add BATCH launchers for Windows. References #180
Improvements to lsc-sample script for cygwin. References #180.
History
Updated by Nicolas Charles 5 months ago
- File lsc.bat added
Correcting an issue of an unset variable that would cause an error
Updated by Rémy-Christophe Schermesser 5 months ago
Thanks Nicolas.
It still does not work :)
The method to build the classpath seems not to appreciate spaces in the path. Here is my error :
C:\Documents and Settings\rcscherm\Mes documents\Téléchargements\lsc-core-1.2-SNAPSHOT-dist.tar\lsc-1.2-SNAPSHOT> C:\WINDOWS\system32\java.exe -cp "";C:\Documents;and;Settings\rcscherm\Mes"" org.lsc.Launcher
Updated by Nicolas Charles 5 months ago
- File lsc.bat added
Using path containing spaces, the previous batch file failed. This batch corrects the issue
Updated by Jonathan Clarke 3 months ago
- % Done changed from 30 to 50
Just tested again on Windows, and we know have a fully-functional lsc launch script in both native Windows console and cygwin. Yay!
However, the lsc-sample script doesn't exist as a .bat (so no native Windows support).
The lsc-sample script runs under cygwin, and successfully imports data into a CSV table. However, launching the LDAP server now causes an error reading the configuration path (I expect that spaces aren't correctly escaped...).
Any help most welcome here!!!
Updated by Jonathan Clarke 3 months ago
- Subject changed from Startup and sample scripts are bash-specific and won't run on Windows without Cygwin to Startup script is bash-specific and won't run on Windows without Cygwin
- Status changed from Feedback to Closed
- % Done changed from 50 to 100
Changing this slightly: this issue now only concerns the bin/lsc startup script. It now works completely on Windows native shell and in Cygwin.
However, the sample still doesn't work correctly in either, so I'm opening another bug to track this: #215. As no one seems very enthusiastic to work on it, I see no reason to hold 1.2.0 up for the sample on Windows... patches welcome, of course.
Updated by Jonathan Clarke 2 months ago
- Target version changed from 1.2.x branch to 1.2.0
This was actually fixed in 1.2.0 and released already. Just updating the bug for records.