Replies: 5 comments 2 replies
-
Yeah, I think we should give that health topic more time to "bake". I'll try to have a closer look at the client generation optimization. |
Beta Was this translation helpful? Give feedback.
-
I would prefer we release 0.9 with the Quarkus 2.0 and other smaller fixes sooner than later. With a major Quarkus upgrade, there could possibly be other issues lurking beneath the surface .... :) The more time we have folk testing this, the better off we are. We can always release 0.9.x versions whenever we have the client generation optimization, health check and other issues / features addressed. So @dufoli Please release away!! |
Beta Was this translation helpful? Give feedback.
-
Release 0.9 is done ... may still need a bit of time to show up in maven central (not sure how long it typically takes) ... Also, we seem to have a ton of (possibly unused) branches ... @dufoli can we clean some of these up? |
Beta Was this translation helpful? Give feedback.
-
When should we expect next release? There were already some fixes, or are we waiting for some specific feature / fix? |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am thinking to release because we have quarkus 2.0 and Uber jar / native issue fixed. Wdyt?
We can optimize generation of clients if it is only used. This is the only issue I found useful to integrate.
The discution on health check lead to no real needs except disable Wsdl with config. We can do it too.
I do not see any other important topic.
Maybe add customization snippets in doc or add configuration to avoid code but not sure...
Beta Was this translation helpful? Give feedback.
All reactions