Can you not update the quarkus version on these extensions? On Mon, Dec 22, 2025 at 10:55 AM Pere Fernandez <[email protected]> wrote:
> Hello folks, > > with a bit of delay, last week I updated the legacy configs classes in all > Quarkus extensions in kogito-runtimes, that was deprecated since 3.19, to > use the new mechanism Quarkus is enforcing ( > https://github.com/apache/incubator-kie-issues/issues/1983). Walter > already did this change in kogito-apps (thank you very much for your help > Walter!!!), and I think Optaplanner was already updated. > > I'd like to make you aware that this legacy mechanism has been completely > dropped since 3.26 ( > https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.26#legacy-config-classes-support-is-gone). > This means that whenever me make the plan to upgrade to a newer Quarkus > version (hopefuly 3.27) we must be sure that all the 3rd party quarkus > extensions we use in our codebase are also aligned and use the new configs > mechanism. > > AFAIK we are using the following extensions from quarkiverse: > - https://github.com/quarkiverse/quarkus-jackson-jq > - https://github.com/quarkiverse/quarkus-asyncapi > - https://github.com/quarkiverse/quarkus-embedded-postgresql > > This extensions are very outdated and still use the old mechansim. I made > an attempt to upgrade them to a new version while fixing this issue but it > was impossible without updating the actual Quarkus version. > > So we should keep in mind that we should update them and adapt the actual > code base to any the new apis they provide before doing the final Quarkus > update. > > Thank you very much! > > Pere > > On 2025/05/31 20:27:23 Tiago Bento wrote: > > Ricardo, > > > > Probably not brand new information as some people are already looking > into > > it AFAIK, just wanted to raise awereness in a more general sense, since > > Quarkus has picked up a good pace in releasing often, so this kind of > > upgrade will be a recurrent task for us. > > > > Regards, > > > > Tiago Bento > > > > On Fri, May 30, 2025 at 17:54 ricardo zanini fernandes < > > [email protected]> wrote: > > > > > Tiago, is this additional information, or are you replying to my > previous > > > email? > > > > > > Cheers! > > > > > > On Fri, May 30, 2025 at 1:11 PM Tiago Bento <[email protected]> > wrote: > > > > > > > Timestamped SNAPSHOTs have not been published for the last two weeks, > > > > potentially impacting the Quarkus 3.20 upgrade on `kie-tools`. A new > > > > timestamped SNAPSHOT publish job will be automatically triggered this > > > > Sunday, but if it fails we'll need to understand why it's failing and > > > > fix it so that the Quarkus 3.20 upgrade can be considered complete. > > > > > > > > On Fri, May 30, 2025 at 12:14 PM ricardo zanini fernandes > > > > <[email protected]> wrote: > > > > > > > > > > Hi Tibor, > > > > > > > > > > Additionally, I think I mentioned to you that now our CI is > breaking > > > due > > > > to > > > > > Keycloak devservices issues in tests. Can you please take a look? I > > > > > believe we should disable these services since they are enabled by > > > > default > > > > > by Quarkus 3.20 IIRC. > > > > > > > > > > Cheers! > > > > > > > > > > On Wed, May 28, 2025 at 1:22 PM Tibor Zimányi <[email protected] > > > > > > wrote: > > > > > > > > > > > Yes, makes sense. Thank you Pere for noticing this. > > > > > > > > > > > > Best regards, > > > > > > Tibor > > > > > > > > > > > > Dňa st 28. 5. 2025, 19:09 Pere Fernandez < > [email protected]> > > > > > > napísal(a): > > > > > > > > > > > > > Hi @Tibor (and all), > > > > > > > > > > > > > > I did a quick test today and I got a warning during startup > > > regarding > > > > > > some > > > > > > > of our Config classes we are using in our extensions / addons. > IRC > > > > > > > since Quarkus 3.15 Quarkus started deprecating the @ConfigRoot > > > > > > annotations > > > > > > > we are using in our configs in favor of Smallrye. So far > everything > > > > works > > > > > > > fine because they keep backwards compatibility (we are using a > > > > specific > > > > > > > flag in our extensions to enable the legacy mechanism) however > it > > > > would > > > > > > be > > > > > > > nice if we migrate to the new mechanism. > > > > > > > > > > > > > > Some of the affected configs are: > > > > > > > > > > > > > > - org.kie.flyway.quarkus.KieFlywayQuarkusRuntimeConfig > > > > > > > - org.kie.kogito.index.addon.config.DataIndexBuildConfig > > > > > > > - org.kie.kogito.index.addon.config.DataIndexRuntimeConfig > > > > > > > - > org.kie.kogito.index.addon.config.DataIndexUIClientRuntimeConfig > > > > > > > - > > > > > org.kie.kogito.job.http.recipient.JobHttpRecipientRuntimeConfiguration > > > > > > > - > > > > > org.kie.kogito.job.sink.recipient.JobSinkRecipientRuntimeConfiguration > > > > > > > - org.kie.kogito.quarkus.config.KogitoBuildTimeConfig > > > > > > > - org.kie.kogito.quarkus.config.KogitoRuntimeConfig > > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > > > > > org.kie.kogito.quarkus.workflow.deployment.config.KogitoWorkflowBuildTimeConfig > > > > > > > > > > > > > > I raised this ticket > > > > > > > https://github.com/apache/incubator-kie-issues/issues/1983 to > fix > > > > it. > > > > > > I'll > > > > > > > try to find time to tackle it during next week. > > > > > > > > > > > > > > Cheers! > > > > > > > > > > > > > > > > > > > > > On Wed, 28 May 2025 at 16:17, ricardo zanini fernandes < > > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > Thanks Tibor! > > > > > > > > > > > > > > > > On Wed, May 28, 2025 at 7:10 AM Tibor Zimányi < > > > [email protected] > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > the PRs for drools, optaplanner, kogito-runtimes, > kogito-apps > > > and > > > > > > > > > kogito-examples were merged. I will continue with kie-tools > > > when > > > > > > there > > > > > > > > is a > > > > > > > > > new weekly build of the libraries. > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > Tibor > > > > > > > > > > > > > > > > > > On Mon, May 26, 2025 at 10:23 AM Tibor Zimányi < > > > > > > > [email protected]> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > I resubmitted the PRs for the Quarkus upgrade. There is > one > > > > problem > > > > > > > > with > > > > > > > > > > serverless workflow test yamls. Some of those contain a > field > > > > > > > > > > "lastTransitionTime", like here (1). There is a current > > > fabric > > > > bug > > > > > > > > around > > > > > > > > > > this (see the link in the comment). How important are > those > > > > > > datetime > > > > > > > > > > fields, please? Because the tests pass without those. Can > > > > someone > > > > > > > from > > > > > > > > > > serverless take a look at those problems? I tried to > override > > > > > > > > > > kubernetes-client to 7.2.0, however that doesn't work as > > > > Quarkus > > > > > > uses > > > > > > > > > > 7.1.0. > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Tibor. > > > > > > > > > > > > > > > > > > > > (1) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/incubator-kie-kogito-runtimes/pull/3935/files#diff-df1637d3c414626b6682e77385559f33418b41f02c0ea46a6c472699a270bf1dR57 > > > > > > > > > > > > > > > > > > > > On Tue, Mar 25, 2025 at 7:00 PM Luiz Motta < > > > [email protected] > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >> +1 > > > > > > > > > >> > > > > > > > > > >> On 2025/03/24 09:53:01 Tibor Zimányi wrote: > > > > > > > > > >> > Hi, > > > > > > > > > >> > > > > > > > > > > >> > Quarkus 3.20.x should be a new LTS stream of Quarkus. > I > > > see > > > > > > 3.20.0 > > > > > > > > > >> > artifacts already public, however there is still no > public > > > > > > > > > announcement > > > > > > > > > >> > yet. Based on this, I think the release is imminent. > > > > Therefore I > > > > > > > > > >> propose to > > > > > > > > > >> > start working on the upgrade so it is prepared as > soon as > > > > > > possible > > > > > > > > > after > > > > > > > > > >> > the Quarkus release. > > > > > > > > > >> > I know we are in the middle of the 10.1 release work, > so I > > > > asked > > > > > > > one > > > > > > > > > of > > > > > > > > > >> the > > > > > > > > > >> > people in the IBM team contributing to KIE (Ann Joy) > to > > > > take a > > > > > > > look > > > > > > > > at > > > > > > > > > >> the > > > > > > > > > >> > work currently, to not slow down any progress on the > > > > release. If > > > > > > > we > > > > > > > > > >> agree > > > > > > > > > >> > it would be good to have this being worked on, I will > try > > > to > > > > > > > manage > > > > > > > > > >> this so > > > > > > > > > >> > it doesn't block the release work in any way. > > > > > > > > > >> > > > > > > > > > > >> > Is there anyone opposing this, please? What do you > think? > > > > > > > > > >> > > > > > > > > > > >> > Best regards, > > > > > > > > > >> > Tibor > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > >> To unsubscribe, e-mail: [email protected] > > > > > > > > > >> For additional commands, e-mail: > [email protected] > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Tibor Zimanyi > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
