[jaxrs] Support jackson option (true by default)
Merged
RI
1y ago+108+108+012345678901234567890123456789-392-392-012345678901234567890123456789
Jackson was a requirement when using the server JAX-RS generator. Removing this requirement allows generating multi-platform code.
The PR is split into 3 commits (with a 4th for updating the samples/docs):
- Allow enabling/disabling jackson, since it was always enabled
- Disabled generating RootResource and RootApplication if generating interfaces, since these files make no sense in the context of generating interfaces
- Update templates to remove jackson references when disabled
The 2nd can be its own PR if required, since not directly relevant to the linked issue. But its a small change and something that makes no sense as it was, so I just added it instead of having to get a reviewer's attention twice.
To fix #6881
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:
(For Windows users, please run the script in WSL)./mvnw clean package || exit ./bin/generate-samples.sh ./bin/configs/*.yaml || exit ./bin/utils/export_docs_generators.sh || exit
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(upcoming7.x.0minor 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. - @martin-mfg Are you the correct person for this?