Hi,
Vincent Fourmond wrote:
- debug output of java version found, and how the java command was found
(it helps a great lot when users ask for help and have e.g. a dangling
environment variable).
When DEBUG_WRAPPERS is set, the JAVA_HOME found is written.
Thanks, my point was also to call jav
Hello,
Eric Lavarde wrote:
> comparing the wrapper script from FreeMind, version 0.9.0, not yet in
> Debian [1], and your script, I'm missing the following features:
>
> - no check that JAVA_CMD actually exists and is executable if the
> variable is set.
I've modified that.
> - /usr/bin/ja
Hi Vincent,
comparing the wrapper script from FreeMind, version 0.9.0, not yet in
Debian [1], and your script, I'm missing the following features:
- no check that JAVA_CMD actually exists and is executable if the
variable is set.
- /usr/bin/java as last fallback if nothing else helps.
- debu
Hello,
Michael Koch wrote:
>>> Before we move stuff into Debian java-common it should be completely
>>> working for most cases.
I've looked at a fair amount of wrapper scripts, and the wrappers.sh
library I propose can be used to provide all their functionalities
easily save one, for bsh, w
Hello,
On Fri, Jan 04, 2008 at 06:18:48PM +0100, Vincent Fourmond wrote:
> Michael Koch wrote:
> > On Fri, Jan 04, 2008 at 04:42:30PM +0100, Vincent Fourmond wrote:
> > java-common in Ubuntu has another mechanism applied to it (but its
> > unused currently). Perhaps its possible to merge stuff fr
Michael Koch wrote:
> On Fri, Jan 04, 2008 at 04:42:30PM +0100, Vincent Fourmond wrote:
> java-common in Ubuntu has another mechanism applied to it (but its
> unused currently). Perhaps its possible to merge stuff from that.
If I read the code right, they just have a list of possible JAVA_HOME
i
On Fri, Jan 04, 2008 at 04:42:30PM +0100, Vincent Fourmond wrote:
>
> Hello,
>
> Michael Koch wrote:
> > "find_java_runtime" is harder. You actually need to run the programs to
> > really find out if a runtime works with a given program.
>
> Well, this approach won't be practical. I preferre
Hello,
Michael Koch wrote:
> "find_java_runtime" is harder. You actually need to run the programs to
> really find out if a runtime works with a given program.
Well, this approach won't be practical. I preferred to use a system of
'capacities' : do we need swing, some of sun's classes, a jav
2007/12/29, Michael Koch <[EMAIL PROTECTED]>:
> On Fri, Dec 28, 2007 at 02:08:33AM +0100, Vincent Fourmond wrote:
Hello Vincent,
Thanks for your suggestion.
> "find_java_runtime" is harder. You actually need to run the programs to
> really find out if a runtime works with a given program.
Maybe
On Fri, Dec 28, 2007 at 02:08:33AM +0100, Vincent Fourmond wrote:
>
> Hello,
>
> Many java packages provide runnable programs living in /usr/bin under
> the form of a wrapper sh script. Most of them use essentially the same
> or very similar code, although some are obviously of much better qu
Hello,
Many java packages provide runnable programs living in /usr/bin under
the form of a wrapper sh script. Most of them use essentially the same
or very similar code, although some are obviously of much better quality
than others.
What about collecting reusable bits of these scripts and
11 matches
Mail list logo
