gvSIG bugs #1437
El arranque de gvSIG no gestiona correctamente la variable JAVA_HOME
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Urgent | Spent time: | - | |
Assignee: | Juan Lucas Domínguez | |||
Category: | Application | |||
Target version: | 2.0.0-rc2 | |||
Severity: | Add-on version: | |||
gvSIG version: | 2.0.0 | Add-on build: | ||
gvSIG build: | 2060 | Add-on resolve version: | ||
Operative System: | Linux | Add-on resolve build: | ||
Keywords: | Proyecto: | |||
Has patch: | Yes | Hito: | ||
Add-on name: | Unknown |
Description
gvsig.sh asigna la variable JAVA_HOME a piñon (línea 11). Se anula el valor de la variable JAVA_HOME.
Además debería tener en cuenta si existe una jre en el directorio gvSIG
History
#1 Updated by Joaquín del Cerro Murciano over 11 years ago
- Category set to Application
- Assignee set to Joaquín del Cerro Murciano
- Target version set to 2.0.0-rc2
#2 Updated by Joaquín del Cerro Murciano over 11 years ago
- File gvSIG.sh added
- Assignee changed from Joaquín del Cerro Murciano to Juan Lucas Domínguez
Adjunto gvSIG.sh con las correcciones.
#3 Updated by Joaquín del Cerro Murciano over 11 years ago
- File gvSIG.sh added
- Has patch changed from No to Yes
Modificado el gvSIG.sh adjunto para que si la encuentra prefiera una java de 32 bits frente a otra de otra arquitectura (ej. 64 bits).
#4 Updated by Juan Lucas Domínguez over 11 years ago
- Status changed from New to Fixed
Fixes management of JAVA_HOME, checks if JRE in gvSIG folder and searches for 32-bit JRE first (file provided by jjdelcerro).
#5 Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed