Could not resolve all dependencies for configuration ':sonar:provided': - unresolved dependency: org.codehaus.sonar#sonar-java-api;2.9: jfrog: unabl e to get resource for org.codehaus.sonar#sonar-java-api;2.9: res=http://repo.jfr og.org/artifactory/gradle-plugins-snapshots/org.codehaus.sonar/sonar-java-api/2. 9/sonar-java-api-2.9-javadoc.jar: org.apache.commons.httpclient.NoHttpResponseEx ception: The server repo.jfrog.org failed to respond
Hmm, wonder if this is a transient issue or not, but a current attempt to build the latest gradle sources fails with the above error. -Spencer --- On Sat, 8/27/11, Luke Daley <[email protected]> wrote: From: Luke Daley <[email protected]> Subject: Re: [gradle-dev] Gradle source bootstrapping To: "[email protected]" <[email protected]> Date: Saturday, August 27, 2011, 2:19 PM You should build with the wrapper as it's more or less guaranteed to work with that version. On 27/08/2011, at 7:02 PM, Spencer Allain <[email protected]> wrote: This might be intentional, but it seems that in order to build the latest source that an existing milestone-4 build is actually needed (or some snapshot leading up to it) since it uses new functionality within gradle itself. Using milestone-3, I didn't even get through buildSrc before gradle/groovyProject.gradle was referenced and things halted on the use of the new output SourceSetOutput object. I'd rather not hit the penalty of milestone-4 always going out to test every dependency, so is there a recommended snapshot prior to the wharf integration or very current with fixes that should be able to compile the latest code without the performance penalty? -Spencer
