This is an automated email from the ASF dual-hosted git repository.
bmarwell pushed a change to branch java17support
in repository https://gitbox.apache.org/repos/asf/shiro.git.
discard dce866d [BUILD] Java 17 support.
add 3f6d112 delete not used jsecurity-sample.jks file
add 17ba345 Merge pull request #320 from ThanoshanMV/SHIRO-836
add 413d5ce [BUILD] Java 17 support.
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 (dce866d)
\
N -- N -- N refs/heads/java17support (413d5ce)
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:
.github/workflows/maven.yml | 6 +++---
.../spring-mvc/src/main/resources/jsecurity-sample.jks | Bin 1250 -> 0 bytes
2 files changed, 3 insertions(+), 3 deletions(-)
delete mode 100644 samples/spring-mvc/src/main/resources/jsecurity-sample.jks
