brmson / yodaqa

A Question Answering system built on top of the Apache UIMA framework.
http://ailao.eu/yodaqa
Other
619 stars 205 forks source link

gradlew check failed! my javasdk is jdk8 #25

Closed andyyuan78 closed 8 years ago

andyyuan78 commented 8 years ago

nvy@ub1404envy:~/os_prj/github/_QA/brmson/yodaqa$ ./gradlew check Downloading https://services.gradle.org/distributions/gradle-2.1-bin.zip .........................................................................................................................................................................................................

https://repo1.maven.org/maven2/org/apache/httpcomponents/httpclient/4.2.6/httpclient-4.2.6.pom Download https://repo1.maven.org/maven2/org/slf4j/jcl-over-slf4j/1.7.6/jcl-over-slf4j-1.7.6.pom Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4.2.5/httpcore-4.2.5.pom Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.2.5/httpcomponents-core-4.2.5.pom Download http://ailao.eu/maven/eu/ailao/gloveDict/1.0-stanford/gloveDict-1.0-stanford.jar :generateTypeSystem FAILED

FAILURE: Build failed with an exception.

BUILD FAILED

Total time: 3 mins 8.85 secs

pasky commented 8 years ago

Did that error persist?

k0105 commented 8 years ago

I think this issue can be closed. It looks very much like a connection error on the user side. I just tested gloveDict and I can obtain it just fine.

@andyyuan78 Have you tried making sure your connection is stable and then just rerunning the build? I'm fairly confident this should fix it.

andyyuan78 commented 8 years ago

it does repeated, but I noticed that it was a download issue..

thanks all

dpny518 commented 6 years ago

How did you fix it? It is a connection issue, I used another machine to download .gradle and got all the files, and uploaded them to /home/username/.gradle/caches/modules-2/files-2.1/eu.ailao/gloveDict/1.0-stanford/81f816cd79944c228c3da08d706f58afacd6a590/gloveDict-1.0-stanford.jar

But I still get the same issue

nagygergo commented 6 years ago

@bambamochu Gradle always checks access to the artifact regardless of having a file to verify it's checksum for security reasons regardless of having it in the cache (you are doing cache tampering which can be used maliciously and build systems try to defend against it).

One solution would be to introduce a locally hosted library for the artifacts you can't access from the computer you are running it on. To do that, make the following changes in the build.gradle file:

//Around line 100

repositories {
  mavenCentral()
  maven {
    url 'http://zoidberg.ukp.informatik.tu-darmstadt.de/artifactory/repo/'
    url 'http://ailao.eu/maven/'
  }
  flatDir {       //Add these rows
    dirs 'libs'   //
  }               //
}

Now you can copy the artifacts that you can't access to <projectRoot>/libs and gradle will find them there.