_JAVA_OPTIONS confuses version check

[Steven R. Loomis]

For reason or reasons unknown (probably related to the old build 
system), I had this in my environment:
     _JAVA_OPTIONS=-Dfile.encoding=ASCII
This causes the shiny new build system's "java -version" to read the 
java version as:
     "Picked up _JAVA_OPTIONS: -Dfile.encoding=ASCII"
and fail version check.

   configure: Found potential Boot JDK using well-known locations (in 
/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk)
configure: Potential Boot JDK found at 
/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home is 
incorrect JDK version (Picked up _JAVA_OPTIONS: -Dfile.encoding=ASCII); 
ignoring
configure: (Your Boot JDK must be version 7 or 8)

-s

On 2/23/13 9:29 AM, Martin Buchholz wrote:
> I'm having fun with the shiny new build system.
> It took me a while to discover that "make help" was exceptionally helpful.
>
> However, I was interested in passing a configuration to CONF= and was
> annoyed there was no clue what to provide.  (I wasn't even sure exactly
> what a "configuration" was)
>
> After some trial and error, I discovered that
>
> make CONF=bogus
>
> would actually give me that precious list of supported configurations.
> It would be nice if "make help" always printed that list, even though by
> default it contains only one entry.