I don’t know if creating a blocker for the next release is necessary, but we do need a ticket to track the work. Yeser or Toni, mind detailing the work and creating a ticket?
-- Jason Porter Software Engineer He/Him/His IBM From: Yeser Amer <ya...@apache.org> Date: Wednesday, August 20, 2025 at 02:24 To: dev@kie.apache.org <dev@kie.apache.org> Subject: [EXTERNAL] Re: [HEADS UP] @ConfigRoot class support getting dropped from Quarkus - Optaplanner, might affect other projects Hi, Side note, I guess we should apply a similar change in other Apache KIE repositories. I found a lot of `-AlegacyConfigRoot=true` occurrences in `kie-kogito-runtimes` On 2025/08/19 14:10:28 Toni Rikkola wrote: > Hi, > > "Legacy @configroot classes support will be dropped soon from Quarkus > and Quarkus 3.15+ already supports @ConfigMapping interfaces so we can > move this project to the new infrastructure. > One thing that is important is that you are currently using runtime > config at static init - which means that it's build time for native > images and this is not correct - and disallowed." > > https://github.com/apache/incubator-kie-optaplanner/pull/3177 > > > To make the PR usable, there would have to be a KIE release and > currently we are blocked to do one. > > Toni Rikkola > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > For additional commands, e-mail: dev-h...@kie.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org For additional commands, e-mail: dev-h...@kie.apache.org
