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

Build warning 'Failed to index boolean ...' in Quarkus < 3.7 #38520

Closed
mschorsch opened this issue Feb 1, 2024 · 4 comments
Closed

Build warning 'Failed to index boolean ...' in Quarkus < 3.7 #38520

mschorsch opened this issue Feb 1, 2024 · 4 comments
Labels
kind/bug Something isn't working triage/out-of-date This issue/PR is no longer valid or relevant

Comments

@mschorsch
Copy link
Contributor

mschorsch commented Feb 1, 2024

Describe the bug

Quarkus < 3.7 shows the following build warning if MediaType.APPLICATION_JSON and return value Boolean. The MediaType is wrong but the error message is not very helpful to identify the problem.

Note: The problem is not reproducible in Quarkus >= 3.7.

[WARNING] [io.quarkus.deployment.steps.CombinedIndexBuildStep] Failed to index boolean: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for code-with-quarkus-1.0.0-SNAPSHOT@33ff6a62

How to Reproduce?

reproducer.zip

./mvnw clean install

Output of java -version

Java 17

Quarkus version or git rev

3.6.9

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

Maven

@geoand
Copy link
Contributor

geoand commented Feb 1, 2024

This was likely fixed in #37456. @Ladicek I believe we can backport it, right?

@geoand geoand added triage/out-of-date This issue/PR is no longer valid or relevant and removed triage/needs-triage labels Feb 1, 2024
@geoand geoand closed this as completed Feb 1, 2024
@Ladicek
Copy link
Contributor

Ladicek commented Feb 1, 2024

Yeah, I think so.

@gsmet
Copy link
Member

gsmet commented Feb 1, 2024

I don't plan on doing any other 3.6 so if it's fixed in 3.7, it's all good (that's what I secretly hoped when I asked for this issue to be opened).

Not sure we would want to backport it to 3.2 (and if it affects 3.2).

@geoand
Copy link
Contributor

geoand commented Feb 1, 2024

I don't plan on doing any other 3.6

Makes sense!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working triage/out-of-date This issue/PR is no longer valid or relevant
Projects
None yet
Development

No branches or pull requests

4 participants