Geek Answers Handbook

Gradle dependency resolution always trying mavenCentral first?

I have a dependency chain that contains javax.jms: jms: 1.1. There is POM in the maven center for this artifact, but there seems to be no bank (problem with the maven center center). However, we do have a local repository containing the artifact we need. So, I think that it would be just like placing our local repository first, and then mavenCentral () last:

repositories {
    maven { url 'http://local-maven:12345/repo' }
    mavenCentral()
}

However, when running gradle -i, we see that he looks at mavenCentral first. Since it finds the POM on mavenCentral, it does not look at any other repository, but after the jar is missing, the assembly fails:

Download http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.pom
Resource missing. [HTTP GET: http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar]
....
* What went wrong:
Execution failed for task 'unzipDependencies'.
> Could not resolve all dependencies for configuration 'compile'.
   > Could not download artifact 'javax.jms:jms:1.1:jms.jar'
      > Artifact 'javax.jms:jms:1.1:jms.jar' not found.

, mavenCentral? maven? , , javax.jms: jms: 1.1: jms.jar ... .

+4
1

. , POM , . , Gradle, Maven Central :

repositories {
    maven {
        url "http://repo1.maven.org/maven2"
        artifactUrls "http://local-maven:12345/repo"          
    }
}
+3

More articles:


All Articles