You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing Micronaut Native Image builds in the scope of #494
I noticed that in case of Micronaut 4 Maven projects, jkube 's MicronautGenerator is not getting picked up, jkube is defaulting to JavaExecGenerator instead.
[INFO] --- k8s:1.17-SNAPSHOT:build (default-cli) @ jkube-micronaut-demo ---
[INFO] k8s: Running generator java-exec
[INFO] k8s: java-exec: Using Docker image quay.io/jkube/jkube-java:0.0.24 as base / builder
[INFO] k8s: [demo/jkube-micronaut-demo:0.1] "java-exec": Created docker-build.tar in 119 milliseconds
[INFO] k8s: [demo/jkube-micronaut-demo:0.1] "java-exec": Built image sha256:759bf
[INFO] k8s: [demo/jkube-micronaut-demo:0.1] "java-exec": Removed old image sha256:d948a
This is happening because in Micronaut 4 groupId of micronaut-maven-plugin has changed from io.micronaut.build to io.micronaut.maven
Describe the bug
I was testing Micronaut Native Image builds in the scope of #494
I noticed that in case of Micronaut 4 Maven projects, jkube 's MicronautGenerator is not getting picked up, jkube is defaulting to JavaExecGenerator instead.
This is happening because in Micronaut 4
groupId
of micronaut-maven-plugin has changed fromio.micronaut.build
toio.micronaut.maven
We need to update this to
io.micronaut.maven
jkube/jkube-kit/jkube-kit-micronaut/src/main/java/org/eclipse/jkube/micronaut/MicronautUtils.java
Line 55 in e1cde0b
Eclipse JKube version
SNAPSHOT
Component
Kubernetes Maven Plugin
Apache Maven version
None
Gradle version
None
Steps to reproduce
k8s:build
(You would see that generator invoked isjava-exec
notmicronaut
Expected behavior
k8s:build
should correctly invoke micronaut generatorRuntime
Kubernetes (vanilla)
Kubernetes API Server version
1.25.3
Environment
Linux
Eclipse JKube Logs
No response
Sample Reproducer Project
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: