+1
From: Pere Fernandez (apache)
Sent: Thursday, February 8, 2024 1:35 AM
To: dev@kie.apache.org
Subject: [EXTERNAL] Re: [PROPOSAL] Drop legacy runtime and KieAssemblerService
Drools integration
+1
On Wed, 7 Feb 2024 at 17:55, Alex Porcelli wrote
+1
On Wed, 7 Feb 2024 at 17:55, Alex Porcelli wrote:
> +1
>
> With the caveat that I expect this will not interfere in the 10.0.0
> release that I expect we'll be able to start the release procedures in
> less than 2 weeks.
>
> On Wed, Feb 7, 2024 at 3:58 AM Gabriele Cardosi
> wrote:
> >
> >
+1
With the caveat that I expect this will not interfere in the 10.0.0
release that I expect we'll be able to start the release procedures in
less than 2 weeks.
On Wed, Feb 7, 2024 at 3:58 AM Gabriele Cardosi
wrote:
>
> Hi Enrique,
> sorry, from your mail I did not get that your suggestion was
Hi Enrique,
sorry, from your mail I did not get that your suggestion was only
relevant to workflow/kogito-runtimes.
I have no knowledge nor opinion on that specific scope
Best
Gabriele
Il giorno mer 7 feb 2024 alle ore 09:46 Enrique Gonzalez Martinez <
elguard...@gmail.com> ha scritto:
> Hi
Hi Gabriele.
I am only talking about workflow engine not other engines.
El mié, 7 feb 2024 a las 9:44, Gabriele Cardosi
() escribió:
>
> HI Enrique,
> there is some clarification needed here.
> 1 KieAssemblerServices were meant to provide a common API to be implemented
> by different engines, to
HI Enrique,
there is some clarification needed here.
1 KieAssemblerServices were meant to provide a common API to be implemented
by different engines, to create a common abstraction usable transparently
2 unfortunately, they have not been implemented thorughfully, resulting in
a sort of
Why remove it ?
At present kogito is based on the premise of a combination of code
generation based on a fluent interface. Nothing at kogito level uses
these parts of KieAssemblerService anymore.
This is causing not moving those test/guards for the functionality in
the new infrastructure causing a
