Resolved dependencies not visible in eclipse buildpath


(Firas Fafi) #1

Hello, I have a situation with gradle dependencies resolution I don’t understand why the resolved jars is not visible in eclipse buildpath. Well here’s how I how I define them

configurations {
  myproject
  }
  repositories {
  flatDir {
    dirs 'local_lib'
    dirs 'libforsonar'
  }
    mavenCentral()
  maven{ url "http://download.java.net/maven/2/" }
  //"jboss"
  maven{ url "https://repository.jboss.org/nexus/content/groups/public/" }
  //"jboss 3rd party"
  maven{ url "https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/"}
  //"spring"
  maven{ url "http://repo.spring.io/libs-release-remote/"}
  //"cloudera"
  maven{ url "https://repository.cloudera.com/content/groups/public/"}
  //"datanucleus"
  maven{ url "http://www.datanucleus.org/downloads/maven2/"}
  //"pentaho"
  maven{ url "http://repository.pentaho.org/artifactory/pentaho/"}
  //"fusesource"
  maven{ url "http://repo.fusesource.com/nexus/content/groups/public/" }
  // to include locale jars
  }
  dependencies {
myproject
//.. some jars
}

Also what does not make sens is that I can successfully compiling with gradle. Can anyone tell me what is wrong? Thank you for your answers


(Peter Niederwieser) #2

By default, only dependencies from standard configurations (‘compile’, ‘runtime’, ‘testCompile’, ‘testRuntime’) will be added to the Eclipse class path. For how to add dependencies from other configurations (e.g. ‘myproject’), see ‘EclipseClasspath’ in the Gradle Build Language Reference.