Mailing-List: contact commits-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@buildr.apache.org
Date: Tue, 29 Jan 2013 02:06:11 +0000 (UTC)
From: "Peter Donald (JIRA)" <jira@apache.org>
To: buildr-commits@incubator.apache.org
Message-ID: <JIRA.12609264.1348672440164.205313.1359425171465@arcas>
In-Reply-To: <JIRA.12609264.1348672440164@arcas>
References: <JIRA.12609264.1348672440164@arcas>
Subject: [jira] [Resolved] (BUILDR-655) Alternative JVMs not working under
 OsX
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BUILDR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald resolved BUILDR-655.
---------------------------------

    Resolution: Fixed

Ok - thanks!
                
> 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
>            Assignee: Peter Donald
>             Fix For: 1.4.8
>
>
> 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