Hi Shawn: You have to give JAVA_HOME to ant as ENVIRONMENT VARIABLE, e.g. "JAVA_HOME=/.../... ant foobar". This makes the ant shell script (which works behind the "ant" command) to use the specified JVM. This makes the code compile with the specified java version.
The 2 special variables JAVA6_HOME and JAVA7_HOME are named a little bit sub-optimal: They are passed as "system properties" and are not interpreted by ant itself. It's used by the build script when executing the smoke tester. More correct would be to pass them not in capital-letters to ANT as system property, like ant -Djava6home=... -Djava7home=..., but its as it is at the moment. JAVA_HOME and the stupid named JAVA6_HOME are two completely different things. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Shawn Heisey [mailto:[email protected]] > Sent: Monday, January 20, 2014 3:02 AM > To: [email protected] > Subject: Re: [VOTE] Release Lucene/Solr 4.6.1 RC1 > > On 1/19/2014 4:04 PM, Mark Miller wrote: > > If you are building the artifacts, you have to make sure it's using > > Java > > 6 rather than 7. IMO on linux, ant picks up what is set by the > > JAVA_HOME env variable. > > The /etc/alternatives links point all the main java executables to 7u25. > 6u26 is available. JAVA6_HOME and JAVA7_HOME were both set. > JAVA_HOME was not. > > I'll do some experimentation ... although I would think that if java 6 is > required, it could use the information it's been given about java 6. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
