Many "Unrecognized configuration key" when adding runtime-tools-quarkus-extension dependency

juangon commented 2 years ago

Describe the bug

When adding

<dependency>
      <groupId>org.kie.kogito</groupId>
      <artifactId>runtime-tools-quarkus-extension</artifactId>
    </dependency>

dependency, it shows a lot of "Unrecognized configuration key".

Expected behavior

Shouldn't warn about any unknown configuration key, if all dependencies were right.

Actual behavior

Many "unrecognized configuration key"

How to Reproduce?

1-Get any quarkus kogito example (tested with process-usertasks-with-security-oidc-quarkus-with-console). 2-Modify pom.xml and add dependency:

<dependency>
      <groupId>org.kie.kogito</groupId>
      <artifactId>runtime-tools-quarkus-extension</artifactId>
    </dependency>

3-./mvnw clean verify. Check warnings about missing configuration keys.

Output of `uname -a` or `ver`

Linux Ubuntu

Output of `java -version`

11

GraalVM version (if different from Java)

No response

Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)

1.22.1

Build tool (ie. output of `mvnw --version` or `gradlew --version`)

No response

Additional information

No response

fjtirado commented 2 years ago

I have already seen this, but I guess it is just a quarkus logging issue that will be eventually solved in later releases. The system is working fine, despite the warnings.

fjtirado commented 2 years ago

The issue is in our plate, we need to let quarkus know which properties we are using

juangon commented 2 years ago

Thanks @fjtirado. I opened other similar case here: https://github.com/kiegroup/kogito-runtimes/issues/2324

cristianonicolai commented 2 years ago

@paulovmr could you take a look regarding dev-ui properties? Persistence ones have been fixed in https://github.com/kiegroup/kogito-runtimes/pull/2335

apache / incubator-kie-kogito-apps