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.

Sign up for GitHub

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

Jump to bottom

beanio extension metadata is not up to date #5803

Closed
aldettinger opened this issue Feb 26, 2024 · 3 comments
Closed

beanio extension metadata is not up to date #5803

aldettinger opened this issue Feb 26, 2024 · 3 comments
Assignees
@jamesnetherton
Labels
area/beanio area/quarkus-platform bug Something isn't working
Milestone
3.9.0

Comments

@aldettinger
Copy link
Contributor

Bug description

While releasing Camel Quarkus 3.8.0, beanio needed to be excluded in the quarkus-platform bom as the quarkus metadata quarkus-extension.yaml was not up to date. It's not possible to override the metadata in quarkus-platform because it does not even contain the artifactId.

The metadata might not be up to date in main and 3.8.x branch.
@aldettinger aldettinger added the bug Something isn't working label Feb 26, 2024
@aldettinger aldettinger self-assigned this Feb 26, 2024
aldettinger added a commit to aldettinger/camel-quarkus that referenced this issue Feb 26, 2024
@aldettinger
update quarkus metadata apache#5803
f11790d
aldettinger added a commit to aldettinger/camel-quarkus that referenced this issue Feb 26, 2024
@aldettinger
update quarkus metadata apache#5803
7b0b9f6
zhfeng pushed a commit that referenced this issue Feb 27, 2024
@aldettinger
update quarkus metadata #5803 (#5805)
16ea3af
zhfeng pushed a commit that referenced this issue Feb 27, 2024
@aldettinger
update quarkus metadata #5803 (#5804)
af8a44c
@jamesnetherton
Copy link
Contributor

Probably because the wrong Maven plugin was declared in the beanio extension:

#5807

@aldettinger
Copy link
Contributor Author

@jamesnetherton would it be more accurate to transfer the ticket ownership to you as you have found the solution ?

@jamesnetherton
Copy link
Contributor

@jamesnetherton would it be more accurate to transfer the ticket ownership to you as you have found the solution ?

Yes, I'll take it.

@aldettinger aldettinger mentioned this issue Feb 27, 2024
Merged
@jamesnetherton jamesnetherton changed the title release: quarkus metadatas are not up to date beanio extension metadata is not up to date Mar 20, 2024
@jamesnetherton jamesnetherton added this to the 3.9.0 milestone Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamesnetherton jamesnetherton

Labels
area/beanio area/quarkus-platform bug Something isn't working
Projects
None yet
Milestone
3.9.0
Development

No branches or pull requests
2 participants
@jamesnetherton @aldettinger