Skip to content

maven report in maven site#5125

Open
junietrytwo wants to merge 1 commit intoswagger-api:masterfrom
junietrytwo:master
Open

maven report in maven site#5125
junietrytwo wants to merge 1 commit intoswagger-api:masterfrom
junietrytwo:master

Conversation

@junietrytwo
Copy link
Copy Markdown

Pull Request

Thank you for contributing to swagger-core!

Please fill out the following information to help us review your PR efficiently.


Description

Hello team,

This PR is to add capability to have the report in the maven site report page.

By maven site report page, I mean this:

404472460-dbd2d2df-a49a-4eba-bc43-551e8780af36

This can be a nice addition and have the report in static page directly

Fixes:

Type of Change

  • 🐛 Bug fix
  • [ X] ✨ New feature
  • ♻️ Refactor (non-breaking change)
  • 🧪 Tests
  • 📝 Documentation
  • 🧹 Chore (build or tooling)

Checklist

  • [ X] I have added/updated tests as needed
  • I have added/updated documentation where applicable
  • [X ] The PR title is descriptive
  • [ X] The code builds and passes tests locally
  • I have linked related issues (if any)

Screenshots / Additional Context

Copy link
Copy Markdown
Contributor

Thank you for contributing!

Could you please provide a bit more context:

  • Which module does this change apply to? (e.g. swagger-maven-plugin, swagger-maven-plugin-jakarta, both?)
  • Is this linked to an existing issue? If so, please add Fixes #<issue-number> to the PR description.
  • The PR branch (master) is currently behind the target branch — could you rebase onto the latest master so we can properly review the diff?

A short description of the expected output and how to verify it (e.g. run mvn site and check the report page) would also help reviewers understand the change quickly. Thanks!


Generated by Claude Code

@ewaostrowska ewaostrowska added the backlog label Apr 23, 2026 — with Claude
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants