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
fabric8 generator cli and maven plugin returning different java method names #5955
Labels
bug
component/java-generator
Waiting on feedback
Issues that require feedback from User/Other community members
Comments
That is a sundrio bug. We'll need to pickup another release to correct that. |
thanks, why would it work fine with the cli though which is also making use of sundrio? |
You must be picking up a different version of sundio that way. |
I'm not able to reproduce this using the maven plugin. Check which version of sundrio you're using.
|
manusa
added
the
Waiting on feedback
Issues that require feedback from User/Other community members
label
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
component/java-generator
Waiting on feedback
Issues that require feedback from User/Other community members
Describe the bug
We are trying to generate Java classes for the following CRD https://github.com/strimzi/strimzi-kafka-operator/blob/affc1968742a8ab1121d23a64c9247ca5c477a32/install/cluster-operator/041-Crd-kafkaconnect.yaml
We set extraAnnotations configuration to generate the fluent builder pattern. Here is what we are noticing
This CRD has a
template
field. With the CLI, the builder has correctwithTemplate
&endTemplate
methodsHowever, with the maven plugin, the builder seems to have
withTemplate
&endKafkaconnectspecTemplate
methodWhat could be the reason?
Fabric8 Kubernetes Client version
6.12.1
Steps to reproduce
Generate the java sources using both the cli and maven fabric8 generator plugin
e.g. cli
Expected behavior
We expected the plugin & the cli to work the same way
Runtime
minikube
Kubernetes API Server version
1.25.3@latest
Environment
Linux, macOS
Fabric8 Kubernetes Client Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: