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
[Quarkus 2.0] Consider following the way how Quarkus handles Avro schemas #2513
Milestone
Comments
WDYT @aldettinger ? |
I guess we should at least document the new option. |
Indeed, I think deprecating |
Thanks, I think we can do this once we have Quarkus 2.0.x in our |
ppalaga
changed the title
Consider following the way how Quarkus handles Avro schemas
[Quarkus 2.0] Consider following the way how Quarkus handles Avro schemas
May 19, 2021
I moved this to the 2.0.0 milestone as I think it'd be good to get this done. Would also be good if we could cover the different schema types avdl, avpr & avsc. |
aldettinger
added a commit
to aldettinger/camel-quarkus
that referenced
this issue
Jun 15, 2021
…me class generation apache#2513
aldettinger
added a commit
to aldettinger/camel-quarkus
that referenced
this issue
Jun 15, 2021
…me class generation apache#2513
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With quarkusio/quarkus#16169 and a couple of other related PRs Quarkus introduced a new approach for compiling Avro schemas. They are now compiled using
generate-code
andgenerate-code-tests
mojos ofquarkus-maven-plugin
. I wonder whether we should recommend the same to our end users and maybe deprecate our@BuildTimeAvroDataFormat
annotation?The text was updated successfully, but these errors were encountered: