Add Maven BOM
envgap__jwtk__jjwt-967
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
5812f63a76084914c5b653025bd3b84048389223- Manifest
pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
jwtk/jjwt #967 · read the original issue
<!-- PLEASE DO NOT USE GITHUB ISSUES TO ASK QUESTIONS! The JJWT team uses GitHub Issues only to track actionable work that requires changes to the JJWT codebase. If you have a usability or general question about JJWT, please instead post your question to StackOverflow using the following JJWT-specific link: https://stackoverflow.com/questions/ask?tags=jjwt&guided=false To help ensure you receive a timely response, please follow the StackOverflow guidelines on how to ask a good question: https://stackoverflow.com/help/how-to-ask Ok, now that that's out of the way - if you're still sure you want to create a feature request or enhancement, please fill in the sections below... --> **Is your feature request related to a problem? Please describe.** Keeping Maven dependency versions consistent is hard. **Describe the solution you'd like** I would like a BOM published to Maven central. **Describe alternatives you've considered** Users of the library can keep their Maven dependency versions consistent properties. **Additional context** Maven BOMs have become a popular method for multi-module library projects to help users keep their dependencies up to date. Many popular libraries publish a BOM, such as [guava](https://central.sonatype.com/artifact/com.google.guava/guava-bom/versions).
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]