[ 
https://issues.apache.org/jira/browse/BUILDR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464229#comment-13464229
 ] 

Peter Donald commented on BUILDR-655:
-------------------------------------

I had a look at this and it looks to be a bug somehow related to the way that 
RJB on OSX works. RJB is the library that Buildr uses to interact with the JVM. 
Essentially RJB does not seem to allow the configuration of the JVM without 
setting some environment variables (possibly at build time?). See 
http://rjb.rubyforge.org/. There are two main ways to work around this - one is 
to use the external compiler by adding something like 
"compile.using(:externaljavac)" into your buildfile, the other alterative is to 
use jruby. I will look into what is required to solve this correctly for the 
next release.

                
> Alternative JVMs not working under OsX
> --------------------------------------
>
>                 Key: BUILDR-655
>                 URL: https://issues.apache.org/jira/browse/BUILDR-655
>             Project: Buildr
>          Issue Type: Bug
>          Components: Compilers
>    Affects Versions: 1.4.7
>         Environment: Mac OsX version 8.2, Ruby 1.9.3, RVM
>            Reporter: James McMahon
>
> Buildr under OsX doesn't seem to respect alternative JVMs defined by the Java 
> Preferences GUI and the JAVA_HOME enviroment variable.
> After attempting to switch over to a 1.7 JVM I was unable to comple my code, 
> Buildr gives a 'javac: invalid source release: 1.7' error. When I disable the 
> system JVM (leaving just the alternative JVM) it gives a 'JavaVM: requested 
> Java version ((null)) not available. Using Java at "" instead.' error.
> Antoine Toulme on Stackoverflow suggested that could be an issue with Buildr 
> not respecting JAVA_HOME on Mac OsX and asked me to create this issue.
> More details can be found at, http://stackoverflow.com/questions/12587089

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to