buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin (JIRA)" <>
Subject [jira] Commented: (BUILDR-289) Verify JAVA_HOME for Improved Error Messages
Date Tue, 23 Jun 2009 18:08:07 GMT


Assaf Arkin commented on BUILDR-289:

tools_jar used to do that, looking for tools.jar (rt.jar is JRE), but turns out it doesn't
exist on all platforms. do we have a guarantee that rj.jar exists on all platforms?

For running executables, those are found with path_to_bin, which complains if JAVA_HOME is
not found, otherwise the call to system does swallow the error message and you need --trace
to figure out what went wrong.

Where do you see "/bin/java does not exist"?

> Verify JAVA_HOME for Improved Error Messages
> --------------------------------------------
>                 Key: BUILDR-289
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Daniel Spiewak
>            Assignee: Daniel Spiewak
>             Fix For: 1.3.5
> Buildr uses the JAVA_HOME environment variable for a number of core tasks.  However,
if that variable does not point to a valid JDK, the result will be a failure at some point
with a generally confusing error message (usually something on the order of " /bin/java does
not exist").  We should actually check to make sure that JAVA_HOME is valid before attempting
to use it for the first time.  This check could be as simple as looking for rt.jar and a few
of the executables.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message