Bump up kogito 1.39.0 / drools 8.39.0

[kie-ci]

Generated by Kogito pipelines

[gsmet]

The last commit is a bit concerning. Removing a component in a micro that late in the 2.16 cycle doesn't look like a good idea.

[gsmet]

/cc @maxandersen ^

[aloubyansky]

Agreed. This doesn't make sense.

[mbiarnes]

afaik OptaPlanner is not released any more together with drools and kogito. But OptaPlanner has a dependency to drools.
If we bump up drools to 8.39.0.Final but we don't bump up OptaPlanner, thean the latter one is pointing to the previous drools 8.38.0.Final version. This was the idea to remove all OptaPlanner stuff in quarkus-platform 2.16

[radtriste]

This is a fair point from Quarkus side. We need to discuss about this on our side ...

[mareknovotny]

if we can lower the relation to Drools and just let Optaplanner as it is, it would be the better option imho.

[aloubyansky]

If you force a new version of drools into the platform, will it actually break OptaPlanner?

[mbiarnes]

@aloubyansky that was the intitial problem why we thought it is better to remove OptaPlanner. OptaPlanner has a dependency to drools. If drools is being upgraded but OptaPlanner not IMO it could be that sooner or later OptaPlanner breaks.

[aloubyansky]

As long as it's compatible though we should be upgrading. You could setup a CI to test OptaPlanner with the relevant branch of Drools to get early status on where this is going. We enforce different versions of Quarkus core regularly in the platform, for example.

[radtriste]

As long as it's compatible though we should be upgrading. You could setup a CI to test OptaPlanner with the relevant branch of Drools to get early status on where this is going. We enforce different versions of Quarkus core regularly in the platform, for example.

Pipeline we already have.
My main concern was to update the Drools version in quarkus-universe-bom because OP defines hard dependencies on Drools. But seems that since we included Drools as a separate project, it is no issue anymore ...
In that case, we will release new version of OP only if Drools is breaking things for it.

[radtriste]

@mbiarnes Can you finalize the PR ?

[kie-ci]

@radtriste finalized drools & kogito

[quarkus-bot]

Failing Jobs - Building 3c8d69e

Status	Name	Step	Failures	Logs	Raw logs
✖	Build - JDK 11	Build with Maven	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Build - JDK 11 #

- Failing:  

📦 Root project

✖ Failed to execute goal io.quarkus:quarkus-platform-bom-maven-plugin:0.0.83:invoke-platform-project (build-platform-project) on project quarkus-platform-config: Failed to build the platform project, please consult the errors logged above.

📦 generated-platform-project/quarkus-camel/integration-tests/camel-quarkus-integration-test-lra

✖ org.apache.camel.quarkus.component.lra.it.LraTest.testLraTransaction - More details - Source on GitHub

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:625)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:696)

[radtriste]

@aloubyansky @gsmet ready to merge

[aloubyansky]

Thanks @radtriste