[
https://issues.apache.org/jira/browse/BUILDR-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723251#action_12723251
]
Assaf Arkin commented on BUILDR-289:
------------------------------------
The contents of rj.jar is part of the JRE spec, I'm not sure about the
location, or that all JDKs will honor it.
Form looking at the code to path_to_bin, setting JAVA_HOME to empty string will
indeed look for /bin/java. I think it will be more reliable for
Java::Commands.java to complain if it can't find java than to depend on
something else looking for indirect hints like existence of rt.jar.
> Verify JAVA_HOME for Improved Error Messages
> --------------------------------------------
>
> Key: BUILDR-289
> URL: https://issues.apache.org/jira/browse/BUILDR-289
> 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.
