GaneshPatil7517 opened a new pull request, #260:
URL: https://github.com/apache/shiro-site/pull/260

   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:
     - Clear Maven and Gradle examples
     - Step-by-step guidance
     - Complete example project
     - Migration instructions from BOM to dependency chain
     
   ✔ Updated Jakarta EE documentation (`jakarta-ee.adoc`) presenting both 
approaches:
     - FlowLogix dependency chain (recommended)
     - Traditional BOM with individual dependencies
   
   ✔ Explanation of benefits over BOM:
     - Single dependency instead of multiple declarations
     - Automatic jakarta classifier configuration
     - Includes all required transitive dependencies
     - Consistent versions across all components
   
   ## 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
   - FlowLogix Dependency Chains: https://docs.flowlogix.com/depchains
   - FlowLogix GitHub: https://github.com/flowlogix/flowlogix
   - Maven Central: https://central.sonatype.com/search?q=com.flowlogix.depchain


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to