Hallo Etienne,
* Etienne Gagnon wrote:
> eclipse -consolelog -vm /usr/bin/sablevm -vmargs
>/usr/bin/sablevm *IS* *NOT* argument compatible with Sun's Java. If
>you want to run SableVM using a Sun compatible argument/environment
>(e.g. $CLASSPATH), you should use /usr/bin/java-sablevm.
Just done
Hallo Etienne,
* Etienne Gagnon wrote:
> eclipse -consolelog -vm /usr/bin/sablevm -vmargs
>/usr/bin/sablevm *IS* *NOT* argument compatible with Sun's Java. If
>you want to run SableVM using a Sun compatible argument/environment
>(e.g. $CLASSPATH), you should use /usr/bin/java-sablevm.
Just done
Hi,
You typed the following:
eclipse -consolelog -vm /usr/bin/sablevm -vmargs
Including user settings ~/.eclipse/eclipserc...
Using /home/jan/workspace for workspace
Using /usr/bin/sablevm as java virtual machine...
/usr/bin/sablevm *IS* *NOT* argument compatible with Sun's Java. If
you wa
Hi,
You typed the following:
eclipse -consolelog -vm /usr/bin/sablevm -vmargs
Including user settings ~/.eclipse/eclipserc...
Using /home/jan/workspace for workspace
Using /usr/bin/sablevm as java virtual machine...
/usr/bin/sablevm *IS* *NOT* argument compatible with Sun's Java. If
you
Hallo Ben,
* Ben Burton wrote:
>> >> and will let the user choose one default VM, which will be used,
>> >> when it is include in your list of 'known working VMs'.
>Not necessarily, just an understanding of what you mean. I'm still
>uncomfortable with using a hand-rolled system here where we have
Hallo Ben,
* Ben Burton wrote:
>> >> and will let the user choose one default VM, which will be used,
>> >> when it is include in your list of 'known working VMs'.
>Not necessarily, just an understanding of what you mean. I'm still
>uncomfortable with using a hand-rolled system here where we have
> >> and will let the user choose one default VM, which will be used,
> >> when it is include in your list of 'known working VMs'.
> >Rightio.
>
> I take that as an agreement?
Not necessarily, just an understanding of what you mean. I'm still
uncomfortable with using a hand-rolled system here w
> >> and will let the user choose one default VM, which will be used,
> >> when it is include in your list of 'known working VMs'.
> >Rightio.
>
> I take that as an agreement?
Not necessarily, just an understanding of what you mean. I'm still
uncomfortable with using a hand-rolled system here w
Hallo Ben,
* Ben Burton wrote:
>> and will let the user choose one default VM, which will be used,
>> when it is include in your list of 'known working VMs'.
>Rightio.
I take that as an agreement?
Another point is, that this is common code and so it should be factored
into some common place. I h
Hallo Ben,
* Ben Burton wrote:
>> and will let the user choose one default VM, which will be used,
>> when it is include in your list of 'known working VMs'.
>Rightio.
I take that as an agreement?
Another point is, that this is common code and so it should be factored
into some common place. I h
> Yes: The findjava script will let you *overwrite* your 'known working
> VMs'
Well, so did that tiny 'for' loop (by allowing the user to set $JAVA).
> and will let the user choose one default VM, which will be used,
> when it is include in your list of 'known working VMs'.
Rightio.
> 'need to
> Yes: The findjava script will let you *overwrite* your 'known working
> VMs'
Well, so did that tiny 'for' loop (by allowing the user to set $JAVA).
> and will let the user choose one default VM, which will be used,
> when it is include in your list of 'known working VMs'.
Rightio.
> 'need to
Hallo Ben
* Ben Burton wrote:
>Since the proposed policy mandates that programs use both these scripts
>(section 2.6), I would really like to see working implementations of
>each of these *before* we look at making this proposal into policy.
A first java-config script is already online:
http://ww
Hallo Ben
* Ben Burton wrote:
>Since the proposed policy mandates that programs use both these scripts
>(section 2.6), I would really like to see working implementations of
>each of these *before* we look at making this proposal into policy.
A first java-config script is already online:
http://ww
Hi. Just a couple of notes re the findjava and java-config scripts.
Since the proposed policy mandates that programs use both these scripts
(section 2.6), I would really like to see working implementations of
each of these *before* we look at making this proposal into policy.
>Packages, whi
Hi. Just a couple of notes re the findjava and java-config scripts.
Since the proposed policy mandates that programs use both these scripts
(section 2.6), I would really like to see working implementations of
each of these *before* we look at making this proposal into policy.
>Packages, whi
Hallo Dalibor,
* Dalibor Topic wrote:
[mention how the unfree VMs should be used]
>I do not quite understand: do you simply want to list the VMs available in
>debian at the time of writing, and include references to non-free VMs not in
>debian?
I want something so that users take one way to incl
Hallo Jan,
--- Jan Schulz <[EMAIL PROTECTED]> wrote:
> I would like to include somewhere teh naming and way to include
> 'unfree' JVM, but I haven't found a proper place. I would like to make
> that a little more specific, so that we only use one way to access
> them (otehrwise there will be some
Hallo Dalibor,
* Dalibor Topic wrote:
[mention how the unfree VMs should be used]
>I do not quite understand: do you simply want to list the VMs available in
>debian at the time of writing, and include references to non-free VMs not in
>debian?
I want something so that users take one way to incl
Hallo Jan,
--- Jan Schulz <[EMAIL PROTECTED]> wrote:
> I would like to include somewhere teh naming and way to include
> 'unfree' JVM, but I haven't found a proper place. I would like to make
> that a little more specific, so that we only use one way to access
> them (otehrwise there will be some
Hallo,
This is the forth attempt of a rewrite of the current debian java
policy. The chanegs to the third version are:
* droped the 'unfree' interfaces
* dropped all the virtual package names (apart from browser plugin)
* a 'java virtual machine' is no handled by a 'findjava' script, which
wil
Hallo,
This is the forth attempt of a rewrite of the current debian java
policy. The chanegs to the third version are:
* droped the 'unfree' interfaces
* dropped all the virtual package names (apart from browser plugin)
* a 'java virtual machine' is no handled by a 'findjava' script, which
wil
22 matches
Mail list logo
