Gradlew乾淨的構建是失敗的春季啓動Java應用程序

我已經下載了Gradle 4.1並保持GRADLE_HOME環境設置和嘗試gradlew clean build。Gradlew乾淨的構建是失敗的春季啓動Java應用程序

它與下面的異常

A problem occurred configuring root project '_app_'. 
> Could not resolve all files for configuration ':classpath'. 
    > Could not resolve org.pitest:pitest-command-line:1.1.10. 
    Required by: 
     project : 
     > Could not resolve org.pitest:pitest-command-line:1.1.10. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy 
     > Could not resolve org.pitest:pitest-command-line:1.1.10. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy 
    > Could not resolve info.solidsoft.gradle.pitest:gradle-pitest-plugin:1.1.10. 
    Required by: 
     project : 
     > Could not resolve info.solidsoft.gradle.pitest:gradle-pitest-plugin:1.1.10. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy 
     > Could not resolve info.solidsoft.gradle.pitest:gradle-pitest-plugin:1.1.10. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy 
    > Could not resolve org.springframework.boot:spring-boot-gradle-plugin:1.5.6.RELEASE. 
    Required by: 
     project : 
     > Could not resolve org.springframework.boot:spring-boot-gradle-plugin:1.5.6.RELEASE. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy 
     > Could not resolve org.springframework.boot:spring-boot-gradle-plugin:1.5.6.RELEASE. 
     > Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy

失敗當我跑在調試模式相同，我可以看到這個

14:18:09.950 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build. 
14:18:10.013 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: [email protected] 
14:18:10.013 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 10: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 
14:18:10.013 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Failure[value=org.gradle.initialization.ReportedException: org.gradle.internal.exceptions.LocationAwareException: A problem occurred configuring root project '_app_'.] from daemon DaemonInfo{pid=7464, address=[093d98c5-c3fb-4d52-8769-f354b16ed886 port:59558, addresses:[/127.0.0.1]], state=Idle, lastBusy=1504514729826, context=DefaultDaemonContext[uid=1fa87ce9-9184-48a6-9489-499fe27fffa0,javaHome=C:\Program Files (x86)\Java\jdk1.8.0_131,daemonRegistryDir=D:\Users\RMuthu\.gradle\daemon,pid=7464,idleTimeout=10800000,daemonOpts=-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]} (build should be done). 
14:18:10.013 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: dispatching class org.gradle.launcher.daemon.protocol.Finished 
14:18:10.013 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 
Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true 

Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could not resolve org.pitest:pitest-command-line:1.1.10. 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.resolveComponentMet 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ComponentMetaDataResolveState.process(ComponentMetaDataResolveState.java:66) 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ComponentMetaDataResolveState.resolve(ComponentMetaDataResolveState.java:58) 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.findBestMatch(RepositoryChainComponentMetaDataResolver.java:13 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.findBestMatch(RepositoryChainComponentMetaDataResolver.java:11 
     at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolveModule(RepositoryChainComponentMetaDataResolver.java:89 
     ... 20 more 
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.gradle.internal.resource.transport.http.AlwaysRedirectRedirectStrategy

來源

2017-09-04 rohith

如果您使用Gradle包裝器（'gradlew'），那麼您下載哪個Gradle版本以及設置了哪個GRADLE_HOME幾乎沒有意義。 Gradle Wrapper的一個大的專家是，你不需要安裝Gradle，只需要Java。包裝器會自動下載並使用該版本針對並正確使用的Gradle版本。所以你的本地安裝的Gradle版本將被忽略。 '/gradle/wrapper/gradle-wrapper.properties'中定義了哪個Gradle版本？你能用'-s'顯示完整的構建輸出嗎？您的調試輸出似乎在相關性之前或之後被裁剪。 – Vampire

distributionUrl = https \：//services.gradle.org/distributions/gradle-4.1-bin.zip – rohith

那麼是的，那麼它是使用4.1。但後一個問題依然存在。 :-) – Vampire

我重新安裝了Java和問題解決。

來源

2017-09-05 10:32:25 rohith

Gradlew乾淨的構建是失敗的春季啓動Java應用程序

回答

相關問題