Closed lhvy closed 1 year ago
Hmm, that might be another failure in the installer. Its probably installing the intel binaries. Switching java home to 2022 forces an intel compiler, so it succeed.
Yes, its installed the intel binaries. Let me figure out why.
@lhvy Not sure if I'm going to be able to get to this tonight, but you can solve this for now by just deleting the maven folder in ~/wpilib/2023
. That will force it to grab all artifacts from maven, which will let you test the Java 17 compiler. You'll just have to be connected to the internet the first build you do.
Describe the bug Just installed WPILib 2023.1.1 Beta 2 macOS ARM version and attempted to build my team's migrated Java code, but was met with
I have since cleaned out my Gradle and Maven caches, created a new example project and attempted to build using the WPILib extension, with no luck. The exact command that is being run is
./gradlew build -Dorg.gradle.java.home="/Users/Lucas/wpilib/2023/jdk"
. Interestingly changing the2023
to2022
causes the build to pass. Perhaps the problem is something to do with the move from Java 11 to 17?I can also confirm that the issue is not internet related or a firewall/blocking issue of any kind, as I am able to download the same dependencies using the WPILib 2022 JDK, and the builds that fail still successfully publish build scans.
To Reproduce Steps to reproduce the behavior:
Expected behavior Dependencies download and project builds successfully
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Entire error message: