gvSIG bugs #774
Add an alert in the plugin generator if gvSIG is running in a JRE
| 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: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Development project wizard (org.gvsig.mkmvnproject) |
Description
If gvSIG is running from a JRE instead of a JDK, the development project wizard won't be able to compile and won't work.
A check must be added when running the project wizard to alert the user if gvSIG is running in a JRE, explaining what to do to run gvSIG from a JDK.
History
#1
Updated by Juan Lucas Domínguez almost 12 years ago
- Assignee set to Juan Lucas Domínguez
#2
Updated by Juan Lucas Domínguez almost 12 years ago
- Status changed from New to In progress
#3
Updated by Juan Lucas Domínguez almost 12 years ago
- Status changed from In progress to Fixed
Try javac in JAVA_HOME (env) and in current JRE (java.home, up one, then bin/javac). If not found, show warning, user decides cancel or continue. Should be tested on Linux.
#4
Updated by Juan Lucas Domínguez almost 12 years ago
- Status changed from Fixed to In progress
#5
Updated by Juan Lucas Domínguez almost 12 years ago
- File msg.jpg added
- Status changed from In progress to Fixed
Changed checking mechanism.
The mvn.bat (Windows) and mvn (Linux) scripts read the env variable JAVA_HOME (perhaps mandatory in Windows?).
So now the checking algorithm is as follows:
- If the javac ant task works on current "java.home" folder (not JAVA_HOME), then we are on JDK and there is no message dialog
- If we are not on JDK but JAVA_HOME is set, then we show short info dialog, but the user can continue anyway
- If we are not on JDK and JAVA_HOME is not set, we show long warning dialog, but the user can continue anyway
I think stopping completely the plugin is too radical. There might be situations we do not consider now.
See attached image msg.jpg for dialog examples
#6
Updated by Juan Lucas Domínguez almost 12 years ago
- Status changed from Fixed to In progress
#7
Updated by Juan Lucas Domínguez almost 12 years ago
- File msg_new.jpg added
- Status changed from In progress to Fixed
Changed checking and warning message (see image msg_new.jpg)
#8
Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed