I recently submitted my open-source pull request to Apache, titled "Add FlowLogix depchain as easier-than-BOM Shiro-Jakarta-EE dependencies (#219)".
Managing Jakarta EE dependencies alongside Apache Shiro can be a real headache when relying solely on traditional Bill of Materials (BOM) files. My PR integrates the FlowLogix dependency chain, offering an even easier alternative that lets developers pull in all the required Shiro-Jakarta-EE dependencies with minimal boilerplate and fewer version conflicts.
The review process was super encouraging! A core maintainer kindly questioned whether one of the transitive dependencies in the depchain might conflict with older Jakarta specs. I replied with my test cases, explaining how the depchain approach safely handles version resolution without forcing unwanted upgrades. They loved the explanation, left a friendly "Looks great, thanks for the contribution!", and merged it shortly after.
Beyond writing the actual code, this experience taught me a ton about enterprise Java ecosystems, dependency management nuances, and open-source etiquette. As a student, seeing my pull request merged into an official Apache project feels surreal. It showed me that open source isn't as intimidating as it seems from the outside, and I’m already looking for my next issue to tackle!