I can see only the jakarta dependencies and version stuff for OSGi
related to this discussion:
https://github.com/apache/shiro/issues/1324
I will try to take a look today but I'm afraid that the best will be to
move all to jakarta in the source code and dependencies, or to have a
new decidated module.
We should remove all javax dependencies in the next major version (3.x?).
Welcome to the javax/jakarta nightmare...
regards,
François
On 30/04/2024 03:37, le...@flowlogix.com wrote:
What do we do about outstanding issues though?
Some more serious (OSGi?)
On Apr 29, 2024, at 9:23 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
It sounds good to me.
Regards
JB
On Sun, Apr 28, 2024 at 8:39 PM <le...@flowlogix.com> wrote:
Hi,
Looks like we are starting go get multiple issues submitted that are already
slated to be fixed in 2.0.1
I am thinking to release 2.0.1 sooner rather than later.
However, there are a few outstanding issues:
https://github.com/apache/shiro/milestone/7
<https://github.com/apache/shiro/milestone/7>
Can you guys look at those 3 issues and advise?
Especially https://github.com/apache/shiro/issues/1025
<https://github.com/apache/shiro/issues/1025> ?
I think we can safely move https://github.com/apache/shiro/issues/953
<https://github.com/apache/shiro/issues/953> to 2.0.2 or alter.
