[Enhancement] Jakarta EE9+ without classifiers

[papegaaij]

Search before asking

• I had searched in the issues and found no similar issues.

Enhancement Request

At the moment Shiro uses the jakarta classifier for jars that have been transformed to the Jakarta EE namespace. This makes it hard to get the dependencies correct, because these jars share their dependencies with the non-Jakarta variants.

Describe the solution you'd like

Many projects have moved their source code to Jakarta EE 9 or higher. Shiro could start version 3 with Jakarta EE 10. It should not be that hard to keep supporting both 2.x and 3.x for some time, as the code is mostly identical.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[lprimak]

That's being discussed currently on the mailing list.
Another topic is to keep base Java version as 11 or take it to 17 or 21.
Your opinion would be welcome.

[papegaaij]

Yes, I know. I'm the one who started the discussion. I would require Java 17. This will be required for Jakarta EE 11 as well. It has good support both in tools and servers. It would make sense to test on 21 as well, as it's the next LTS and servers like WildFly will make this the recommended SE version soon (probably WildFly 32 or 33).