This is an automated email from the ASF dual-hosted git repository.
lprimak pushed a change to branch 3.x
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit 73f2c58ca chore: supporting updates
omit ff9d48595 [support] Update Karaf feature and bundle maven plugin
configuration (#2517)
omit 129854ecd [#1585] Jakarta namespace and java 17 for 3x (#2017)
omit b4fa93ec6 enh: introduce multi-release jar fixes #1984
omit 3ff64bb40 enh[3.x]: Adds default NoAccess configuration to the default
filter chain (#2461)
omit aff26bd97 [#1585] Migrate to Jakarta EE 10 (3.x) (#2018)
omit 959ed0425 chore(3.x): Migrate to jakarta EE 10 using OpenRewrite
(#2224)
omit 42b72f993 [project] Add 3.X change guidelines
omit 89ba0e87a Set pom version to 3.0.0-SNAPSHOT
omit 2a491da58 Refactor: AssertJ best practices by @timtebeek
omit 1d3becf5c GitHub issue #1548. Declare PrincipalCollection interface to
be intended to be immutable; provide an immutable implementation including a
builder class; deprecate the mutable implementation; use the immutable one in
SimpleAuthenticationInfo for merging.
add 0910a8d3a GitHub issue #1548. Declare PrincipalCollection interface to
be intended to be immutable; provide an immutable implementation including a
builder class; deprecate the mutable implementation; use the immutable one in
SimpleAuthenticationInfo for merging.
add d5982a88c Refactor: AssertJ best practices by @timtebeek
add 9c5c36b1a Set pom version to 3.0.0-SNAPSHOT
add 253e4cfd1 [project] Add 3.X change guidelines
add 8a06174f5 chore(3.x): Migrate to jakarta EE 10 using OpenRewrite
(#2224)
add 833be21e0 [#1585] Migrate to Jakarta EE 10 (3.x) (#2018)
add 20616c247 enh[3.x]: Adds default NoAccess configuration to the default
filter chain (#2461)
add f1e053ef9 enh: introduce multi-release jar fixes #1984
add 4120ee904 [#1585] Jakarta namespace and java 17 for 3x (#2017)
add 0c723ce9e [support] Update Karaf feature and bundle maven plugin
configuration (#2517)
add 5b626dc6d chore: supporting updates
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (73f2c58ca)
\
N -- N -- N refs/heads/3.x (5b626dc6d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
