Open jorsol opened 1 month ago
This is known problem with com.marcnuri.plugins:gradle-api-maven-plugin.
Originally tracked in https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/package.20org.2Egradle.2Ewrapper.20does.20not.20exist/
It happens because the content of one of the Gradle distribution jars is different if downloaded from Maven Central or the Gradle distribution itself.
Gradle exposes a tiny fraction of their distribution Jars in Maven Central. It also adds additional stuff to these Jars so there's no need to publish additional artifacts that contain some of the other required classes present in the standard distribution.
The gradle-api-maven-plugin
downloads the jars from the standard Gradle distribution and places them in your local Maven repository.
If you're building Quarkus and the Fabric8 Kubernetes Client, depending on which project you built first, you might get these sort of problems when building the Gradle-related modules for either project.
A simple mvn -U
to force the download of the Gradle dependencies should fix the issue. Keep in mind that if then you switch to Quarkus you might need to do that there too.
The problem will be fixed one https://github.com/manusa/gradle-api-maven-plugin/pull/28 is merged.
Describe the bug
Building the project using
mvn clean package -DskipTests
and fails with:Fabric8 Kubernetes Client version
SNAPSHOT
Steps to reproduce
mvn clean package -DskipTests
Expected behavior
Build success
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
1.25.3@latest
Environment
Linux
Fabric8 Kubernetes Client Logs
No response
Additional context
No response