Kirill A. Korinsky

@barracuda156 I know you have something not clang friendly and old. May I ask you to check this PR? Is it required or should be closed?

=> let close it as useless

@essandess which java version have you use?

@essandess the root cause of issue: `java` PG doesn't respect `java.version 11` and tries to build it on JDK17 and JDK17 is supported since 7.0.0: https://github.com/bazelbuild/bazel/pull/14040 ``` DEBUG: java-portgroup: Trying...

@essandess I've opened a PR into your branch which fixes CI: https://github.com/essandess/macports-ports/pull/2 The run: https://github.com/catap/macports-ports/actions/runs/4860773891 Let unblock it!

@cjones051073 yes, the issue that Github runners has 3rd party JDK. As soon as I've removed it, the CI had passed. I think that ignoring 3rd party JDKs isn't the...

> > @cjones051073 yes, the issue that Github runners has 3rd party JDK. As soon as I've removed it, the CI had passed. > > I think that ignoring 3rd...

@cjones051073 that's wired. The diff below fixes an issue, see: https://github.com/catap/macports-ports/actions/runs/4861461977 ```diff --- a/_resources/port1.0/group/java-1.0.tcl +++ b/_resources/port1.0/group/java-1.0.tcl @@ -165,7 +165,9 @@ namespace eval java { ui_debug "java-portgroup: Detected JVMs: $versions_found" #...

Good, it doesn't fix it. Very good. I was too fast :)

> However to judge if thats the case or not we need to see the _raw_ output from > > ``` > /usr/libexec/java_home -V > ``` > > when run...