Use automatic module dependency for javax.inject package

[jfallows]

When building modular components based on airline, the following message is displayed during compilation.

[INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ ry ---
[WARNING] ********************************************************************************************************************
[WARNING] * Required filename-based automodules detected. Please don't publish this project to a public artifact repository! *
[WARNING] ********************************************************************************************************************

This is caused by the javax.inject dependency which is missing the Automatic-Module-Name entry from the JAR manifest, so the module name is derived from the JAR filename instead. Although the JAR filename is not expected to change for the javax.inject dependency, a JAR filename is not considered sufficiently stable to derive a module name in the general case, triggering the compilation warning above.

As explained by the Transition from Java EE to Jakarta EE blog post, the javax namespace is migrating to jakarta going forward, so this is a good first step towards fully modular jakarta based dependencies for javax.inject.

This pull request addresses the issue by changing the dependency to use an alternative dependency that delivers an automatic module for javax.inject package instead.

[coveralls]

Pull Request Test Coverage Report for Build 537

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.01%) to 71.612%

---

Files with Coverage Reduction	New Missed Lines	%
airline-core/src/main/java/com/github/rvesse/airline/restrictions/common/PortRangeImpl.java	1	68.97%
<!--	Total:	1		-->

Totals
Change from base Build 535:	0.01%
Covered Lines:	5565
Relevant Lines:	7771

---

💛 - Coveralls

[rvesse]

Thanks for the contribution, I remain pretty ignorant of JPMS so thanks for digging into this and resolving it 👍

[jfallows]

@rvesse when do you think you would be able to roll a 2.8.1 release with these changes please?

[rvesse]

@jfallows Probably next week, busy with security scramble at $dayjob for the sudo CVE atm

[rvesse]

@jfallows Just worked through the release this morning, may take a few hours before the artifacts are visible on Maven central

[jfallows]

@rvesse thanks, I just updated the dependency to 2.8.1 and it is working out great! 👍