Search Unity

  1. Are you interested in providing feedback directly to Unity teams? Sign up to become a member of Unity Pulse, our new product feedback and research community.
    Dismiss Notice

Gradle Build fails after upgrade to 2018.2.0b7

Discussion in '2018.2 Beta' started by jakobgalbavy, Jun 9, 2018.

  1. jakobgalbavy

    jakobgalbavy

    Joined:
    Nov 3, 2016
    Posts:
    2
    Hi,

    i just upgraded to 2018.2.0b7 via Unity Hub, removed the old version and started my workspace. Unfortunately, gradel build now fails with the following mesage:


    CommandInvokationFailure: Gradle build failed.
    /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/bin/java -classpath "/Applications/Unity/Hub/Editor/2018.2.0b7/PlaybackEngines/AndroidPlayer/Tools/gradle/lib/gradle-launcher-4.2.1.jar" org.gradle.launcher.GradleMain "-Dorg.gradle.jvmargs=-Xmx2048m" "assembleRelease"

    stderr[

    FAILURE: Build failed with an exception.

    * What went wrong:
    A problem occurred configuring root project 'gradleOut'.
    > java.io.FileNotFoundException: /Applications/Unity/Hub/Editor/2018.2.0b6/PlaybackEngines/AndroidPlayer/Tools/gradle/lib/plugins/gradle-diagnostics-4.2.1.jar (No such file or directory)
    [...........]


    So basically, what happens is, gradle is started from the correct directory, but searches a jar in the old one. How can i change that? I couldn't find it in any configuration option anywhere.
     
  2. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    2,707
unityunity