Quarkus: 1.7.0.CR1 Has dependency on jars not in Maven central

Created on 4 Aug 2020  路  5Comments  路  Source: quarkusio/quarkus

Describe the bug
Build on 1.6.1.Final no longer work on 1.7.0.CR1 due to this dependency which is in gradle repository only and not many people would have that repo set up.

[INFO]
[INFO] ---------------------< org.acme:code-with-quarkus >---------------------
[INFO] Building code-with-quarkus 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
Downloading from central: https://repo.maven.apache.org/maven2/org/gradle/gradle-tooling-api/6.5/gradle-tooling-api-6.5.pom
[WARNING] The POM for org.gradle:gradle-tooling-api:jar:6.5 is missing, no dependency information available
Downloading from central: https://repo.maven.apache.org/maven2/org/gradle/gradle-tooling-api/6.5/gradle-tooling-api-6.5.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.296 s
[INFO] Finished at: 2020-08-04T14:35:12+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project code-with-quarkus: Could not resolve dependencies for project org.acme:code-with-quarkus:jar:1.0.0-SNAPSHOT: Could not find artifact org.gradle:gradle-tooling-api:jar:6.5 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

Expected behavior
Non-default repositories should not be needed to build

Actual behavior
[ERROR] Failed to execute goal on project code-with-quarkus: Could not resolve dependencies for project org.acme:code-with-quarkus:jar:1.0.0-SNAPSHOT: Could not find artifact org.gradle:gradle-tooling-api:jar:6.5 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

To Reproduce
Build any project which has quarkus bom and no custom repositories set

aremaven kinbug triagduplicate

All 5 comments

/cc @quarkusio/devtools

Having the same issue. In our project we only have access to an Artifactory instance that is only connected to jcenter and maven central.

This has already been fixed. I will start the backports to the 1.7 branch so that you can validate it's fixed.

I believe this is a duplicate of #11141

This should be fixed in CR2 now available.

Was this page helpful?
0 / 5 - 0 ratings