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

4.x: Get rid of WARNINGs when starting quickstart #9019

Open
barchetta opened this issue Jul 19, 2024 · 1 comment · May be fixed by #9613
Open

4.x: Get rid of WARNINGs when starting quickstart #9019

barchetta opened this issue Jul 19, 2024 · 1 comment · May be fixed by #9613
Assignees

Comments

@barchetta
Copy link
Member

Environment Details

  • Helidon Version: 4.1.0-SNAPSHOT
  • Helidon MP

Problem Description

I created the quickstart using the cli

helidon init  --reset --url file:///Users/jdipol/GitHub/barchetta/helidon/archetypes/archetypes/target/cli-data

Build and run it and you get WARNINGs:

2024.07.19 16:41:59 WARNING io.helidon.openapi.OpenApiFeature Thread[#1,main,5,main]: Static OpenAPI file not found, checked: [META-INF/openapi.json, META-INF/openapi.yaml, META-INF/openapi.yml]

2024.07.19 16:41:59 WARNING org.glassfish.jersey.message.internal.MessagingBinders Thread[#1,main,5,main]: A class jakarta.activation.DataSource for a default provider MessageBodyWriter<jakarta.activation.DataSource> was not found. The provider is not available.

2024.07.19 16:41:59 WARNING org.glassfish.jersey.server.wadl.WadlFeature Thread[#1,main,5,main]: JAX-B API not found . WADL feature is disabled.

WADL?? Seriously?

I know two of these are from Jersey, but it would be good to get them cleaned up.

@barchetta
Copy link
Member Author

barchetta commented Oct 31, 2024

PR #9451 fixed the warning from OpenApiFeature and org.glassfish.jersey.server.wadl.WadlFeature

That leaves the MessagingBinders warning. See eclipse-ee4j/jersey#5480 for more info on that.

@barchetta barchetta moved this from Normal priority to In Progress in Backlog Oct 31, 2024
@barchetta barchetta linked a pull request Dec 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants