Skip to content

[java][jaxrs-spec][quarkus] - Add @ResponseStatus annotation with status code for success codes (2xx, 3xx) in Quarkus library#1

Open
Ignacio-Vidal wants to merge 1 commit intomasterfrom
java-quarkus-respnose-status
Open

[java][jaxrs-spec][quarkus] - Add @ResponseStatus annotation with status code for success codes (2xx, 3xx) in Quarkus library#1
Ignacio-Vidal wants to merge 1 commit intomasterfrom
java-quarkus-respnose-status

Conversation

@Ignacio-Vidal
Copy link
Copy Markdown
Owner

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@Ignacio-Vidal Ignacio-Vidal marked this pull request as ready for review April 26, 2026 22:16
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch 3 times, most recently from c15921f to 30ea37b Compare April 27, 2026 18:44
@Ignacio-Vidal Ignacio-Vidal changed the title feat: add ResponseStatus annotation for non-200 success codes in Quarkus library [java][jaxrs-spec][quarkus] - Add @ResponseStatus annotation with status code for success codes (2xx, 3xx) in Quarkus library Apr 27, 2026
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch 2 times, most recently from daf076f to 4f7b018 Compare April 28, 2026 21:21
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch from b8f0eb8 to 2917ce8 Compare May 1, 2026 08:12
@Ignacio-Vidal Ignacio-Vidal reopened this May 1, 2026
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch from 045501b to 2917ce8 Compare May 1, 2026 08:44
@Ignacio-Vidal Ignacio-Vidal reopened this May 1, 2026
@Ignacio-Vidal Ignacio-Vidal marked this pull request as draft May 1, 2026 08:49
@Ignacio-Vidal Ignacio-Vidal marked this pull request as ready for review May 1, 2026 23:25
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch 4 times, most recently from 638fc8b to c457142 Compare May 3, 2026 08:15
@Ignacio-Vidal Ignacio-Vidal force-pushed the java-quarkus-respnose-status branch from c457142 to 7db4e0c Compare May 3, 2026 09:33
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.

1 participant