Skip to content

Jandex index missing for signals artifact #23111

@mcollovati

Description

@mcollovati

When building a native Vaadin Quarkus application that uses signals, the following warning message is displayed

[WARNING] [io.quarkus.deployment.steps.ReflectiveHierarchyStep] Unable to properly register the hierarchy of the following classes for reflection as they are not in the Jandex index:
        - tools.jackson.databind.JsonNode (sources: <unknown> > com.vaadin.signals.Node > tools.jackson.databind.JsonNode, <unknown> > com.vaadin.signals.SignalCommand > tools.jackson.databind.JsonNode, <unknown> > com.vaadin.signals.SignalCommand$PutCommand > tools.jackson.databind.JsonNode, <unknown> > com.vaadin.signals.SignalCommand$ValueCondition > tools.jackson.databind.JsonNode)
Consider adding them to the index either by creating a Jandex index for your dependency via the Maven plugin, an empty META-INF/beans.xml or quarkus.index-dependency properties.

Despite the warning message, the application seems to work fine, but it would be good to prevent this warning from being shown by either providing the Jandex index for the signals library (or updating existing indexes, flow-jandex and vaadin-core-jandex)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions