possible bug in mx/projects handling

Doug Simon doug.simon at oracle.com
Mon Jun 3 07:01:32 PDT 2013

On May 31, 2013, at 11:02 PM, "Venkatachalam, Vasanth" <Vasanth.Venkatachalam at amd.com> wrote:

> Hi,
> 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?

I tried to reproduce this by creating a local com.amd.sumatra project and used some JDK 1.8 API in it. However, 'mx build' does the expected thing in may case (i.e. does not try to compiled anything in com.amd.sumatra). Could you please send me the output of 'mx clean --no-native; mx -v build' so I can investigate further.


More information about the graal-dev mailing list