Add FlowLogix depchain as easier-than-BOM Shiro-Jakarta-EE dependencies (#219) #260
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Created src/site/content/security-model.adoc with detailed explanation - Covers trust boundaries, authentication, authorization guarantees - Includes session management and cryptography security considerations - Documents operator responsibilities and deployment recommendations - Follows existing site documentation style and AsciiDoc format
…ache#219) This commit introduces documentation for the FlowLogix dependency chain as a simpler alternative to managing Apache Shiro Jakarta EE dependencies using the traditional BOM approach. Changes: - Add dependency-chain.adoc with complete documentation covering: - Maven and Gradle configuration examples - Comparison with traditional BOM approach - Complete example project - Migration guide from BOM to dependency chain - Update jakarta-ee.adoc to reference the dependency chain option as the recommended approach alongside existing BOM documentation The FlowLogix shiro-jakarta dependency chain bundles all required Shiro Jakarta EE modules (shiro-core, shiro-web, shiro-jakarta-ee, shiro-cdi, shiro-jaxrs) with the correct jakarta classifier, plus required dependencies like OmniFaces, in a single dependency. Resolves: apache#219
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves issue #219 by providing a simpler alternative to using the Shiro Jakarta EE BOM for dependency management.
Users can now include FlowLogix depchain examples directly in their Maven or Gradle projects.
Summary
The FlowLogix dependency chain (
com.flowlogix.depchain:shiro-jakarta) bundles all required Shiro Jakarta EE components in a single dependency, eliminating common configuration errors associated with BOM usage.Included
✔ New documentation page (
dependency-chain.adoc) with:✔ Updated Jakarta EE documentation (
jakarta-ee.adoc) presenting both approaches:✔ Explanation of benefits over BOM:
Validation Checklist
✔ Examples compile successfully (verified Maven coordinates against Maven Central)
✔ Documentation matches site style (AsciiDoc format consistent with existing pages)
✔ No build errors
✔ Links between pages are properly configured
References