Build failing with newly generated Optaplanner App

[alexander-dammeier]

Describe the bug I generated a Quarkus app with your start coding tool. Look here for my configuration.

Expected behavior New app can be built and tested.

Actual behavior Optaplanner fails while testing.

PS ...\course-timetabling> .\gradlew build

Welcome to Gradle 6.4.1!
...
> Task :test

ExampleResourceTest > testHelloEndpoint() FAILED
    java.lang.RuntimeException at QuarkusTestExtension.java:390
        Caused by: java.lang.RuntimeException at AugmentActionImpl.java:246
            Caused by: io.quarkus.builder.BuildException at Execution.java:115
                Caused by: java.lang.IllegalStateException at OptaPlannerProcessor.java:184

1 test completed, 1 failed

> Task :test FAILED

FAILURE: Build failed with an exception.
...
BUILD FAILED in 7s

To Reproduce Steps to reproduce the behavior:

1. download my configured app
2. try to build it with .\gradlew build

Maybe the problem occurs because there are no optaplanner annotations present yet?

[geoand]

cc @ge0ffrey

[ge0ffrey]

Looking at this. cc @triceo in case this spills over to next week when I am on PTO already.

[ge0ffrey]

Thank you for reporting.

Maybe the problem occurs because there are no optaplanner annotations present yet?

Probably, that's an open issue (see https://issues.redhat.com/browse/PLANNER-1957 ). The IllegalStateException occurs if you add the optaplanner extension but don't add any domain etc in the current version. That being said, it's a big pita - and I presumed gsmet we 'd fix it.

It just got pushed out a few times. The complexity is that it must fail fast if there are a subset of the reqs (planning solution, planning entity, constraint provider), but not all. It must only not fail fast if there are none.

[ge0ffrey]

@geoand @alexander-dammeier This issue was fixed a long time ago. Please close it.

[gsmet]

Thanks @ge0ffrey !