gvSIG bugs #773
Launcher in windows uses always a JRE if available
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Juan Lucas Domínguez | |||
Category: | - | |||
Target version: | 2.0.0-alpha6 | |||
Severity: | Add-on version: | |||
gvSIG version: | 2.0.0 | Add-on build: | ||
gvSIG build: | 2048 | Add-on resolve version: | ||
Operative System: | Windows | Add-on resolve build: | ||
Keywords: | Proyecto: | |||
Has patch: | No | Hito: | ||
Add-on name: | Unknown |
Description
In windows, the gvSIG launcher always uses a JRE if available, without taking into account if the user has a JDK installed and has added it in the environment variables as the default one.
This is a problem for developers, as is one has installed the last JDK and JRE, the last one will be used and the plugin generator won't be able to work, as it needs to compile the generated sources.
To solve it, in the launch4j configuration, in the JRE tab, the current option of JRE preference must be changed to:
"Prefer JDK runtime, but use public JRE if newer".
It won't solve every case but maybe most of them.
History
#1 Updated by Juan Lucas Domínguez almost 12 years ago
- Status changed from New to Fixed
Updated two Launch4j XML files (remember some full paths must be updated to your workspace).
#2 Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed