Is your feature request related to a problem? Please describe.
Now that #20 is merged, we have a proper module-info.class starting with version 2.0.1. Great job! 💪
However, this only targets the 2.x branch with its jakarta namespace. Many libraries still use the javax.inject.* package and don't want any breaking changes.
Describe the solution you'd like
I'd therefore propose to backport the module-info to 1.x using the module name java.inject and export package javax.inject.
Describe alternatives you've considered
Convince library vendors to switch to jakarta namespace. Even if successful, this would delay adoption until the next major version to avoid breaking changes.
Additional context
We have discussed potential compatibility issues with older Java versions in #20 and decided to use the MR-Jar approach to avoid such problems.
Is your feature request related to a problem? Please describe.
Now that #20 is merged, we have a proper
module-info.classstarting with version 2.0.1. Great job! 💪However, this only targets the 2.x branch with its jakarta namespace. Many libraries still use the
javax.inject.*package and don't want any breaking changes.Describe the solution you'd like
I'd therefore propose to backport the module-info to 1.x using the module name
java.injectand export packagejavax.inject.Describe alternatives you've considered
Convince library vendors to switch to jakarta namespace. Even if successful, this would delay adoption until the next major version to avoid breaking changes.
Additional context
We have discussed potential compatibility issues with older Java versions in #20 and decided to use the MR-Jar approach to avoid such problems.