Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misleading 'unrecognized configuration' warnings for quarkus.debug.transformed-classes-dir and quarkus.debug.generated-sources-dir #27778

Closed
holly-cummins opened this issue Sep 7, 2022 · 2 comments · Fixed by #28312
Assignees
Labels
area/core kind/bug Something isn't working
Milestone

Comments

@holly-cummins
Copy link
Contributor

Describe the bug

https://quarkus.io/guides/writing-extensions suggests the following debug options:

There are also three system properties that allow you to dump the generated/transformed classes to the filesystem and inspect them later, for example via a decompiler in your IDE.

quarkus.debug.generated-classes-dir - to dump the generated classes, such as bean metadata
quarkus.debug.transformed-classes-dir - to dump the transformed classes, e.g. Panache entities
quarkus.debug.generated-sources-dir - to dump the ZIG files; ZIG file is a textual representation of the generated code that is referenced in the stack traces

All of the options produce the expected output, but there are warnings in the log for the transformed classes and generated sources options (but not the generated classes):

2022-09-07 10:45:32,489 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.debug.generated-sources-dir" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-09-07 10:45:32,489 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.debug.transformed-classes-dir" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

I can't see any different handling in the code for the three options, so I'm not sure why one doesn't get a warning and two do.

Expected behavior

Since these are valid options, there should not be a warning in the log.

Actual behavior

2022-09-07 10:45:32,489 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.debug.generated-sources-dir" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-09-07 10:45:32,489 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.debug.transformed-classes-dir" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

How to Reproduce?

Any Quarkus application should reproduce; I used an application of my own and also the getting started app.

quarkus create app org.acme:getting-started \
    --extension=resteasy-reactive
cd getting-started
mvn quarkus:dev -Dquarkus.debug.transformed-classes-dir=transformed -Dquarkus.debug.generated-classes-dir=generated -Dquarkus.debug.generated-sources-dir=sources

Output of uname -a or ver

Darwin hcummins-mac 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64

Output of java -version

openjdk version "17.0.2" 2022-01-18 OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8) OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode)

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.12.0.Final

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

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)

Additional information

No response

@holly-cummins holly-cummins added the kind/bug Something isn't working label Sep 7, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 30, 2022

@gsmet gsmet self-assigned this Sep 30, 2022
gsmet added a commit to gsmet/quarkus that referenced this issue Sep 30, 2022
@gsmet
Copy link
Member

gsmet commented Sep 30, 2022

Taken care of here: #28312 .

@quarkus-bot quarkus-bot bot added this to the 2.14 - main milestone Sep 30, 2022
@gsmet gsmet modified the milestones: 2.14 - main, 2.13.1.Final Sep 30, 2022
gsmet added a commit to gsmet/quarkus that referenced this issue Oct 3, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 17, 2022
tmihalac pushed a commit to tmihalac/quarkus that referenced this issue Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants