Skip to content

[http-problem] Rename maven coordinates, java packages, examples#604

Merged
lwitkowski merged 12 commits into
mainfrom
480-rename-to-http-problem
May 9, 2026
Merged

[http-problem] Rename maven coordinates, java packages, examples#604
lwitkowski merged 12 commits into
mainfrom
480-rename-to-http-problem

Conversation

@lwitkowski
Copy link
Copy Markdown
Collaborator

@lwitkowski lwitkowski commented May 5, 2026

@lwitkowski lwitkowski changed the title [WIP] #480 Renamed artifact group to http-problem, packages, examples #480 Renamed artifact group to http-problem, packages, examples May 5, 2026
@lwitkowski lwitkowski marked this pull request as ready for review May 5, 2026 19:40
@lwitkowski lwitkowski mentioned this pull request May 5, 2026
9 tasks
@lwitkowski
Copy link
Copy Markdown
Collaborator Author

@pazkooda if you have some time or spare tokens for a quick review - pls have a look. It does not have to be perfect from the get go, we need more changes and stabilization phase either way.

@pazkooda
Copy link
Copy Markdown
Collaborator

pazkooda commented May 6, 2026

Will try to look at it today early afternoon (CET)

Copy link
Copy Markdown
Member

@xstefank xstefank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but can you please revert back the support for RESTEasy classic Jackson and JSON-B? We are still going to ship them also in Quarkus 4, and it would most likely break your extension users on 3.x right now.

Comment thread .github/workflows/quickstart-tests.yaml Outdated
Comment thread runtime/pom.xml Outdated
Co-authored-by: Martin Stefanko <xstefank122@gmail.com>
@lwitkowski
Copy link
Copy Markdown
Collaborator Author

Looks good, but can you please revert back the support for RESTEasy classic Jackson and JSON-B? We are still going to ship them also in Quarkus 4, and it would most likely break your extension users on 3.x right now.

I wasn't sure about this, but that's an excellent point, let me revert this back.

Comment thread deployment/pom.xml
<artifactId>quarkus-resteasy-problem-deployment</artifactId>
<name>Quarkus - RESTeasy - Problem - Deployment</name>
<artifactId>quarkus-http-problem-deployment</artifactId>
<name>Quarkus - HTTP-Problem - Deployment</name>
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cosmetic: HTTP-Problem, we used REST ;)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I've changed all places to HTTP-Problem and pushed it around the time you were reviewing this. And you commented the line where it's already updated. So let's clarify - which option are you suggesting again?

@lwitkowski
Copy link
Copy Markdown
Collaborator Author

TLDR

I believe we should go with the following:

  • maven coordinates io.quarkiverse.httpproblem:quarkus-http-problem
  • Java root package io.quarkiverse.httpproblem
  • config prefix quarkus.http-problem

WDYT @xstefank @pazkooda ? Once we're on the same page, I'll update the groupId (remove extra hyphen).

Longer story

This avoids implying ownership of a shared io.quarkiverse.http.* / quarkus.http.* family and stays consistent with Quarkiverse conventions (groupId as package-safe root; multi-word project suffix concatenated).
Reference: Quarkiverse NamingConventions.

For context, the old resteasy.problem shape reflected historical alignment with the RESTEasy family; the rename intentionally decouples that and uses an extension-specific namespace.

Similar examples in Quarkiverse:

  • GitHub App (standalone extension, no family)

    • maven coordinates io.quarkiverse.githubapp:quarkus-github-app
    • Java root package io.quarkiverse.githubapp
    • config prefix quarkus.github-app
  • Config Consul (family-style namespace)

    • maven coordinates io.quarkiverse.config:quarkus-config-consul
    • Java package namespace under io.quarkiverse.config...
    • config prefix quarkus.consul-config

@xstefank
Copy link
Copy Markdown
Member

xstefank commented May 7, 2026

@lwitkowski thanks, that is perfect. Let me know when I should take a look at this PR again!

@lwitkowski lwitkowski changed the title #480 Renamed artifact group to http-problem, packages, examples #480 [http-problem] Rename maven coordinates, java packages, examples May 7, 2026
@lwitkowski
Copy link
Copy Markdown
Collaborator Author

@lwitkowski thanks, that is perfect. Let me know when I should take a look at this PR again!

@xstefank I think I've applied all the changes I planned, so please have another look when you have time. Thanks!

@lwitkowski lwitkowski changed the title #480 [http-problem] Rename maven coordinates, java packages, examples [http-problem] Rename maven coordinates, java packages, examples May 7, 2026
Copy link
Copy Markdown
Member

@xstefank xstefank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @lwitkowski

Comment thread README.md Outdated
Co-authored-by: Martin Stefanko <xstefank122@gmail.com>
@lwitkowski
Copy link
Copy Markdown
Collaborator Author

@pazkooda I'm merging this now, we can always change things later. I'd like to publish snapshot to Maven Central and play around with it.

@lwitkowski lwitkowski merged commit 2b74a21 into main May 9, 2026
6 checks passed
@lwitkowski lwitkowski deleted the 480-rename-to-http-problem branch May 9, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants