Hello,
I am umpgrading ~200 old projects to Gradle 6.9.1 atm. Many of the dependencies are available in custom maven repositories, but without pom files. I found the solution for this to be
maven {
url "http://repo.mycompany.com/repo"
metadataSources {
mavenPom()
artifact()
}
}
such that Gradle will resolve sole artifacts as well. This works absolutely fine for the repository it was declared in. Artifacts are build and published in a maven. Sadly, some of the ~200 repositories depend on each other and
metadataSources {
mavenPom()
artifact()
}
is not translated into their maven POM file. Therefore, subsequent dependencies will fail to resolve those old dependencies, unless they declare the repository in the same manner. Is there a ways to allow for transitive repositories in this case?
Glad about any suggestions! Cheers,
Sin