Skip to content

HibernateOrmProcessor causes Warning that package cannot be indexed due to package-info.java #50572

@gako

Description

@gako

Describe the bug

If I want to define a global Hibernate @FilterDef the best practive way is to use a package-info.java next to the entities.

But this package-info.java during tests causes a WARN:

2025-10-15 10:38:52,125 WARN [io.qua.dep.ind.IndexWrapper] (build-26) Failed to index org.acme: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@7446d8d5

HibernateOrmProcessor.generateProxies calls the IndexWrapper.getClassByName with the packageName and not an actual className as expected this causes the mentioned warn.

Everything seems to work fine expect the warning so, it probably would be enough to somewhere in HibernateORMProcessor filter out packages from the list of classes.

Expected behavior

Test should run without producing an WARN message each time.

Actual behavior

2025-10-15 10:38:52,125 WARN [io.qua.dep.ind.IndexWrapper] (build-26) Failed to index org.acme: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@7446d8d5

Message is shown during test runs if package-info.java is present with hibernate @FilderDef inside.

How to Reproduce?

code-with-quarkus.zip

Output of uname -a or ver

No response

Output of java -version

21.0.2

Quarkus version or git rev

3.28.3

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

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions