gvSIG bugs #4062
gvSIG 2.3 build 2416 win-x86 installs in 64-bits program files folder
| Status: | Invalid | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | Installer | |||
| Target version: | 2.3.0-2420 (rev. org.gvsig.desktop-2.0.126) | |||
| Severity: | Blocker | Add-on version: | ||
| gvSIG version: | 2.3.0 | Add-on build: | ||
| gvSIG build: | 2416 | Add-on resolve version: | ||
| Operative System: | Windows | Add-on resolve build: | ||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
gvSIG 2.3 build 2416 win-x86 installs in 64-bits program files folder - C:/Program Files/ -, instead of 32-bits one - C:\Program Files (x86)\ -. See the gvSIG-launcher.log in attachment.
History
#1
Updated by Antonio Falciano about 8 years ago
This issue is due to the fact that the installer is executed by Java 64-bits double-clicking on it (I've associated jar to the Java 64-bit application), even if I've set JAVA_HOME as x86.
Only if I execute the installer from the prompt:
"%JAVA_HOME%"\bin\java -jar gvSIG-desktop-2.3.0-2419-devel-win-x86-standard.jarI can force to use Java 32-bits and so gvSIG is installed in C:\Program Files (x86)\ correctly.
This kind of issues (mixed together with different user experiences) could be avoided wrapping the jars for Windows with launch4j that allows to specify which Java version to use when executing the installer, like you did in the past.
In short, is it planned to wrap the installers for win with launch4j within the 2.3 final release?
#2
Updated by Joaquín del Cerro Murciano about 8 years ago
Antonio Falciano wrote:
...
In short, is it planned to wrap the installers for win with launch4j within the 2.3 final release?
Si que esta pensado generar "exes" para la instalacion de windows usando el launch4j, de hecho ya he intentado generar alguno (build 2419 win64), pero aun no esta automatizado. De momento los hago a mano, forzando usar jres de 32 0 64 segun toque.
#3
Updated by Antonio Falciano about 8 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2420 (rev. org.gvsig.desktop-2.0.126)
- Status changed from New to Invalid
Hi Joaquín,
thank you for the explanation. So we can set this ticket as invalid, being only a temporary issue due to a specific configuration.