Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve 
you *grin*, but are you sure? The reason I ask is (barring some really bizarre 
misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and 
I'm getting the error.

Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526

On 2/14/18, 6:53 PM, "build-dev on behalf of Jonathan Gibbons" 
<build-dev-boun...@openjdk.java.net on behalf of jonathan.gibb...@oracle.com> 
wrote:

    
    
    On 2/14/18 4:38 PM, Ted Neward wrote:
    > I’m getting a weird error in my OpenJDK 10 (tip) build, where after 
pulling source and configure, I get a build error about the Java compiler being 
executed with “--module-path” as a parameter, which obviously isn’t a 
legitimate javac flag.
    >
    >   
    I can't speak to your specific build error, but --module-path is a 
    legitimate javac option, as of JDK 9.
    
    -- Jon
    
    >
    > Is this just me? Is anybody else able to repro this, and is there a fix 
coming that isn’t checked into the main trunk yet?
    >
    >   
    >
    > I am in the process of finalizing some Docker images (both with the 
source inside the image and built, so people can just “go”, as well as images 
with the prereqs and some shell scripts to do the build with the source and 
build artifacts on the host machine), and this is holding up the current “tip” 
images from being really ready for public consumption. (JDK8u and JDK9 are up 
and ready to go.)
    >
    >   
    >
    > Ted Neward
    >
    > Author, Speaker, Mentor
    >
    > http://www.newardassociates.com
    >
    > t: @tedneward | m: (425) 647-4526
    >
    
    


Reply via email to