[
https://issues.apache.org/jira/browse/BUILDR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932248#action_12932248
]
Rhett Sutphin commented on BUILDR-549:
--------------------------------------
Yes, that's a known bug in RJB on OS X with Java Update 3 -- it's a side effect
of its fallback mechanism when it is looking for the JNI headers. It looks for
$JAVA_HOME/include. If that's not present, it looks for
$JAVA_HOME/Home/include. If neither are present, it reports the error against
the latter, making it seem buggier than it is.
I worked around the install problem in RJB 1.2.5 by finding a JDK on OS X that
has the include directory (
/Library/Java/JavaVirtualMachines/1.6.0_22-b04-307.jdk/Contents/Home ) and
setting JAVA_HOME to point to that. That allows RJB to install, but it still
doesn't _work_ -- it still has the "can't create Java VM" problem.
Since that workaround didn't work, I started looking into getting buildr to
work with a more-recent version of RJB. In version 1.3.2, RJB will install
using the standard OS X path for JAVA_HOME, but it continues to have the "can't
create Java VM" problem, both on its own and inside of buildr.
> Buildr cannot create a JVM using MRI on OS X 10.6 with Java Update 3 installed
> ------------------------------------------------------------------------------
>
> Key: BUILDR-549
> URL: https://issues.apache.org/jira/browse/BUILDR-549
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.4.1, 1.4.2, 1.4.3
> Environment: OS X 10.6.5 with Java Update 3 for OS X 10.6; tested
> with 1.8.7-p174 and 1.8.7-p302, but probably any MRI will have this problem
> Reporter: Rhett Sutphin
> Attachments: buildfile, trace.txt
>
>
> Java Update 3 for OS X changed the way the JDK is installed on OS X and, in
> the process, broke RJB. With the current trunk, buildr's specs will not run.
> They give the error "RuntimeError : can't create Java VM". Buildfiles which
> invoke java have the same problem.
> Allegedly, upgrading to rjb 1.3.2 will fix this problem. My initial efforts
> in this direction have not been successful. I'll investigate further and
> update this ticket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
