possible bug in mx/projects handling

Venkatachalam, Vasanth Vasanth.Venkatachalam at amd.com
Fri May 31 14:02:28 PDT 2013


We have a project com.amd.sumatra which requires java 1.8 compliance to build.

We've added lines in mx/project to specify that the project shouldn't be built when building with a 1.7 JDK:

distribution at GRAAL@path=graal.jar
distribution at GRAAL@dependencies=com.oracle.graal.hotspot.amd64,com.oracle.graal.hotspot.sparc,com.oracle.graal.hotspot,com.amd.sumatra

# com.amd.sumatra
project at com.amd.sumatra@subDir=graal
project at com.amd.sumatra@sourceDirs=src
project at com.amd.sumatra@dependencies=com.oracle.graal.hotspot,com.oracle.graal.hotspot.amd64,com.oracle.graal.hsail,com.oracle.graal.compiler.hsail,com.amd.okra
project at com.amd.sumatra@checkstyle=com.oracle.graal.graph
project at com.amd.sumatra@javaCompliance=1.8

When I do an mx build, I see the lines

Excluding com.amd.sumatra fro build (Java compliance level 1.8 required)

But then Graal goes ahead and tries to build the package. This appears to be a bug. Can someone look into this?


More information about the graal-dev mailing list