1 |
Problem is, the SenchaCmd script runs java directly, which resolves to |
2 |
/usr/bin/java, which itself is a script that checks the user choice |
3 |
regarding the selected java-vm: setting JAVA_HOME does nothing to fix that. |
4 |
I can edit the SenchaCmd script to run java directly, that would be the |
5 |
quickfix. |
6 |
|
7 |
Thanks for the input. |
8 |
|
9 |
Em seg, 1 de fev de 2016 às 13:41, Alon Bar-Lev <alonbl@g.o> |
10 |
escreveu: |
11 |
|
12 |
> On 31 January 2016 at 19:17, Leonardo Guilherme |
13 |
> <leonardo.guilherme@×××××.com> wrote: |
14 |
> > |
15 |
> > Hello. |
16 |
> > |
17 |
> > I'm using OpenJDK JVM regularly on my machine instead of Oracle's one, |
18 |
> primarily because of the infinality patches and because I prefer open |
19 |
> source software. |
20 |
> > |
21 |
> > There are some applications, though, that do not play ball with it |
22 |
> (namely, SenchaCmd) and I have to keep switching back and forth between |
23 |
> installed java-vms just to run it. |
24 |
> > |
25 |
> > I know nothing about Java or its environment, is there a way to specify |
26 |
> the java-vm just for this application instead of doing "eselect java-vm set |
27 |
> user 1; sencha *stuff*; eselect java-vm set user 3" everytime? |
28 |
> > |
29 |
> > Is there a set of environment variables that can do this? Shall I wrap |
30 |
> the command in a shell script? Ideas? |
31 |
> |
32 |
> Usually, every [well behaved] java application has JAVA_HOME or |
33 |
> similar environment variable to tell it where java is. |
34 |
> You can find a valid java homes at /usr/lib/jvm/*/jre or if you |
35 |
> manually extracted oracle it will probably live in /opt/xxx. |
36 |
> |
37 |
> What you should do is go over this SenchaCmd startup script and find |
38 |
> what it expects. |
39 |
> |
40 |
> Regards, |
41 |
> Alon |
42 |
> |
43 |
> |