gvSIG bugs #4317
gvsig-desktop.cmd: ${INSTALL_DRIVE} is not recognized (in the portable)
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Joaquín del Cerro Murciano | |||
Category: | Application | |||
Target version: | 2.3.0-2445 (rev. org.gvsig.desktop-2.0.152) | |||
Severity: | Minor | Add-on version: | ||
gvSIG version: | 2.3.0 | Add-on build: | ||
gvSIG build: | 2441 | Add-on resolve version: | ||
Operative System: | Windows | Add-on resolve build: | ||
Keywords: | Proyecto: | |||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
When we execute gvSIG double-clicking on the gvsig-desktop.cmd file on Windows, the console reports that ${INSTALL_DRIVE} is not recognized and it's impossible to find a specified path (i.e. ${INSTALL_DRIVE}). Fortunately is not a blocking issue.
I suggest to brutally simplify the content of gvsig-desktop.cmd batch script as:
@echo off busybox sh gvSIG.sh
Related issues
Associated revisions
refs #4317, Añadida la expansion de variables que realiza el instalador en los ficheros de la portable
History
#1 Updated by Joaquín del Cerro Murciano over 7 years ago
Parece un problema del instalador, ya que esas variables deberian sustituirse por sus valores correspondientes en el momento de la instalacion.
Al Izpack se le indica:
<pack name="gvSIG desktop commons windows" required="yes"> <description>Core common files for Windows platforms</description> <file src="${product.folder}/gvsig-package-installer.cmd" targetdir="$INSTALL_PATH"/> <file src="${product.folder}/gvsig-desktop.cmd" targetdir="$INSTALL_PATH"/> <file src="${product.folder}/gvsig-desktop.vbs" targetdir="$INSTALL_PATH"/> <file src="busybox.exe" targetdir="$INSTALL_PATH"/> <file src="cygcheck.exe" targetdir="$INSTALL_PATH"/> <parsable targetfile="$INSTALL_PATH/gvsig-package-installer.cmd"/> <parsable targetfile="$INSTALL_PATH/gvsig-desktop.cmd"/> <parsable targetfile="$INSTALL_PATH/gvsig-desktop.vbs"/> </pack>
De forma que el Izpack, para los dos cmd y el vbs, deba sustituir esas variables.
Cuando pueda lo mirare.
Lo de quitar las lineas esas del cmd no hes del todo correcto ya que si se ha instalado en una unidad distinta a la C no funciona. Por eso se añadieron.
#2 Updated by Joaquín del Cerro Murciano over 7 years ago
- Related to gvSIG bugs #4316: gvsig-desktop.vbs: Unable to find the requested file added
#3 Updated by Joaquín del Cerro Murciano over 7 years ago
- Related to deleted (gvSIG bugs #4316: gvsig-desktop.vbs: Unable to find the requested file)
#4 Updated by Joaquín del Cerro Murciano over 7 years ago
- Duplicated by gvSIG bugs #4316: gvsig-desktop.vbs: Unable to find the requested file added
#5 Updated by Joaquín del Cerro Murciano over 7 years ago
Hola Antonio,
por un correo en la lista me he dado cuenta de un error que puede estar relacionado con este.
A un usuario le pasa lo mismo. Esta ejecutando la portable. En la portable no se realizan las sustituciones del instalador ya que no hay instalador.
¿ A ti te pasa en la portable o en una instalación normal ?
#6 Updated by Antonio Falciano over 7 years ago
Hi Joaquín,
this issue happens in the portable, also in build 2442.
#7 Updated by Joaquín del Cerro Murciano over 7 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2443-RC3 (rev. org.gvsig.desktop-2.0.150)
- Subject changed from gvsig-desktop.cmd: ${INSTALL_DRIVE} is not recognized to gvsig-desktop.cmd: ${INSTALL_DRIVE} is not recognized (in the portable)
#8 Updated by Joaquín del Cerro Murciano over 7 years ago
- Target version changed from 2.3.0-2443-RC3 (rev. org.gvsig.desktop-2.0.150) to 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153)
- Assignee set to Joaquín del Cerro Murciano
- Status changed from New to Fixed
#9 Updated by Joaquín del Cerro Murciano over 7 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2443-RC3 (rev. org.gvsig.desktop-2.0.150)
#10 Updated by Antonio Falciano over 7 years ago
The issue persists only in the console in RC4, there's not trace in the gvSIG-launcher.log but the gvSIG Installation folder is correctly found, so it's not a blocking issue, but only a cosmetic one.
#11 Updated by Joaquín del Cerro Murciano over 7 years ago
- Target version changed from 2.3.0-2443-RC3 (rev. org.gvsig.desktop-2.0.150) to 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153)
- Status changed from Fixed to New
#12 Updated by Joaquín del Cerro Murciano over 7 years ago
- Status changed from New to Fixed
#13 Updated by Joaquín del Cerro Murciano over 7 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2445 (rev. org.gvsig.desktop-2.0.152)
#14 Updated by Álvaro Anguix over 7 years ago
- Status changed from Fixed to Closed