-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to build Fabric8 :: Java generator :: Gradle Plugin #6163
Fail to build Fabric8 :: Java generator :: Gradle Plugin #6163
Comments
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 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 The problem will be fixed once manusa/gradle-api-maven-plugin#28 is merged. |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
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
The text was updated successfully, but these errors were encountered: