Hi!
The Apache Maven project migrated from JIRA to GitHub.
I want to propose the same.
Before we vote, those options were considered for Apache Maven:
1/ try to migrate issues and make JIRA read only
2/ make all our JIRA projects unable to create new issues and new issues
would be raised on
+1
Thanks Lenny!
On Wed, 2 Jul 2025, 02:14 , wrote:
> This is a call to vote in favor of releasing Apache Shiro version 2.0.5
>
> Maven Staging repo:
> https://repository.apache.org/content/repositories/orgapacheshiro-1066
>
> https://repository.apache.org/content/repositories/orgapacheshiro-
+1
Thanks, Lenny!
On Fri, 20 Jun 2025, 17:34 Brian Demers, wrote:
> Hi folks!
>
> This was discussed on Slack, but we need an official vote thread!
>
> Lenny has been a Shiro committer and PMC member for the last few years and
> has been helping move the project forward!
> I'd like to nomina
Hi, I am not able to test this properly in the next two weeks. :(
I wonder: If a servlet starts threads, should the thread not be able
to see the SecurityManager?
Can you give us some more insights?
- Ben
Am Sa., 12. Apr. 2025 um 23:17 Uhr schrieb :
>
> Hi,
>
> During testing of Shiro 2.0.3, I
+1
Ben
Am Sa., 5. Apr. 2025 um 23:38 Uhr schrieb :
>
> This is a call to vote in favor of releasing Apache Shiro version 2.0.3
>
> Maven Staging repo:
> https://repository.apache.org/content/repositories/orgapacheshiro-1063
> https://repository.apache.org/content/repositories/orgapacheshiro-1063/
Dear Devs and users,
a few day ago a discussion in Slack came up about shiro.ini. It is the
number one feature Shiro is known for, and it's certainly not going away.
However, it draws in a few extra dependencies (beanutils, collections 3,
etc).
OTOH, we don't really provide a convenient way to us
Thanks, LGTM!
On Wed, 12 Mar 2025, 17:51 Jean-Baptiste Onofré, wrote:
> Hi Brian
>
> It looks good to me,
>
> Thanks
> Regards
> JB
>
> On Wed, Mar 12, 2025 at 5:25 PM Brian Demers wrote:
> >
> > The 2024 March ASF board report is due today. I've created an initial
> > draft here:
> >
> > ht
Reproducibility checked on Linux using JDK 17.
+1 (binding)
Am Do., 7. Nov. 2024 um 02:38 Uhr schrieb :
>
> This is a call to vote in favor of releasing Apache Shiro version 2.0.2
>
> Maven Staging repo:
> https://repository.apache.org/content/repositories/orgapacheshiro-1062
> https://repository
+1
On Thu, 11 Jul 2024, 08:02 Jean-Baptiste Onofré, wrote:
> +1
>
> ActiveMQ is still on Shiro 1.x. I will prioritize to update to Shiro 2.x.
>
> Regards
> JB
>
> On Tue, Jul 2, 2024 at 6:13 AM wrote:
> >
> > Here is my proposal:
> >
> > Shiro 1.x EOL at the end of 2024
> > Shiro 2.x EOL at t
+1, JavaEE is dead. The band aid should be the other way around now:
classifier for javax, but the code defaults to jakartaee.
We can do that until we use features which are not available in JavaEE.
Am Mo., 11. März 2024 um 14:11 Uhr schrieb Francois Papon
:
>
> Hi,
>
> As we released the Shiro 2
+1
On Tue, 7 Nov 2023, 23:56 , wrote:
> This is a call to vote in favor of releasing Apache Shiro version
> 2.0.0-alpha-4
>
> Maven Staging repo:
> https://repository.apache.org/content/repositories/orgapacheshiro-1057
>
> https://repository.apache.org/content/repositories/orgapacheshiro-1057
+1 for GH actions.
Given we can get the credentials, I'd prefer those.
I agree with Lenny about the flexibility of Jenkins, but GH actions are
easier to browse and to understand. I'd be willing to give up the minimal
flexibility gain of Jenkins for the advantages we get with GH
Actions(-only).
-
+1
Am Di., 31. Okt. 2023 um 10:13 Uhr schrieb fpapon :
>
> Hi everyone,
>
> I submit Apache Shiro 1.13.0 release to your vote.
>
> Release Notes:
> https://github.com/apache/shiro/releases/tag/shiro-root-1.13.0
>
> Staging Maven repository:
> https://repository.apache.org/content/repositories/org
+1
On Wed, 14 Jun 2023, 21:11 Brian Demers, wrote:
> The 2023 June ASF board report is due today (sorry for the late notice).
> I've created an
> initial draft here:
>
> https://svn.apache.org/repos/asf/shiro/board/2023-06.txt
>
> Comments, suggestions, and feedback are welcome. Otherwise,
Since we all agreed here, I will now open the GitHub issues and discussions
in the next few days. If you're faster than me, feel welcome to do it
earlier. 😉
- Ben
On Thu, 27 Apr 2023, 14:39 Benjamin Marwell, wrote:
> +1 for starting fresh.
> Since github is easier to get to, w
+1 for starting fresh.
Since github is easier to get to, we will soon have enough issues to work
on. ;-)
Am Mi., 26. Apr. 2023 um 17:31 Uhr schrieb Colm O hEigeartaigh <
cohei...@apache.org>:
> +1, especially since new users having to manually be approved to signup to
> JIRA.
>
> Colm.
>
> On We
Big +1
On Sat, 1 Apr 2023, 01:31 , wrote:
> BIG +1 for me.
> Even easier, just have old issues in JIRA and new ones in GH.
> Also maybe GH discussions as well?
>
> > On Mar 31, 2023, at 8:40 AM, Brian Demers wrote:
> >
> > We received a suggestion from the last board report to consider switc
+1
Ben
On Sun, 8 Jan 2023, 03:27 Brian Demers, wrote:
> This is a call to vote in favor of releasing Apache Shiro version 1.11.0.
>
> NOTE: This is the second attempt at this release, additional fixes
> for SHIRO-889 have been added since the previous attempt.
>
> We solved 2 Issues:
>
>
> h
+1 (Binding)
On Wed, 4 Jan 2023, 01:54 Brian Demers, wrote:
> This is a call to vote in favor of releasing Apache Shiro version 1.11.0.
>
> We solved 2 Issues:
>
>
> https://issues.apache.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jql=project%20%3D%20SHIRO%20AND%20fixVersion%20%3D%201
+1
On Thu, 8 Dec 2022, 22:22 , wrote:
> This will enable people to at least try to use modern Jakarta and JPMS
> without enabling snapshots and adding Apache snapshot repo
>
>
The Shiro team is pleased to announce the release of Apache Shiro
version 1.10.1.
This security release contains 5 fixes since the 1.10.0 release and is
available for Download now [1].
Bug
[SHIRO-892] - No Guice binding for newly introduced ShiroFilterConfiguration
[SHIRO-893] - NPE caused by la
Hi,
The vote has passed with the following result:
+1: François Papon, Jean-Baptiste Onofré, Brian Demers, Benjamin Marwell
PMC quorum: reached
I will promote the source release zip file to the Apache distribution area and
the artifacts to the central repo.
- Ben
ote.jspa?projectId=12310950&version=12352460
>
> On Tue, Nov 15, 2022 at 12:23 PM Jean-Baptiste Onofré
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On Mon, Nov 14, 2022 at 9:20 PM Benjamin Marwell
> > wrote:
> > >
> >
This is a call to vote in favor of releasing Apache Shiro version 1.10.1.
We solved 5 Issues:
https://issues.apache.org/jira/projects/SHIRO/versions/12352460
Maven Staging repo:
https://repository.apache.org/content/repositories/orgapacheshiro-1043/
https://repository.apache.org/content/reposito
+1, thanks for preparing the report!
On Fri, 16 Sept 2022, 10:25 Jean-Baptiste Onofré, wrote:
> Hi,
>
> It looks good to me with the additional points.
>
> Thanks!
> Regards
> JB
>
> On Wed, Sep 14, 2022 at 5:15 PM Brian Demers
> wrote:
> >
> > Good points!
> >
> > I added:
> >
> > - Work is
+1
By the way: Not all modules are reproducible yet.
Am Do., 23. Juni 2022 um 21:31 Uhr schrieb Brian Demers :
>
> This is a call to vote in favor of releasing Apache Shiro version 1.9.1.
>
> We solved 6 Issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHIRO%20AND%20fixVersi
Hi everyone,
I'd suggest we create a blog post on shiro.apache.org that we might
provide a shaded version of Shiro with the "jakarta" classifier soon.
It seems to draw attention.
What do you think?
Ben
Hi Brian,
thanks, good hints with javax and asking the board a question!
Am So., 12. Juni 2022 um 09:29 Uhr schrieb Francois Papon
:
>
> LGTM!
>
> Thanks Brian!
>
> regards,
>
> François
>
> On 08/06/2022 19:04, Brian Demers wrote:
> > The 2022 June ASF board report is due today. I've created an
Hi everyone!
We now have a staging action, so the site gets deployed to staging
automatically.
It is a manual run, and you need to select the source branch which
should get deployed.
https://github.com/apache/shiro-site/actions/workflows/staging.yml
On the blue bar, click the "Run workflow" drop
Signature okay, hashes okay, Release notes are okay, the classes I
looked at are okay as well.
+1
Am Mi., 16. März 2022 um 13:55 Uhr schrieb Francois Papon
:
>
> This is a call to vote in favor of releasing Apache Shiro version 1.9.0.
>
> We solved 20 issues for 1.9.0:
>
> https://issues.apache.o
Hi Mike!
Thanks for your suggestion! I do like the idea, but we need to make it
fit into Shiro's existing API without changing/breaking it. Extending
is okay.
I couldn't find any other LDAP/AD fields you're referencing. Some
(like email) would need to be settable.
I can imagine LDAP and AD realms
ere are no strong requirements with a particular
> hash, but it's required to have any mechanism to verify source artifacts.
> So, as it's an easy fix, I agree that it would be better to cancel this vote
> to include sha512 hash on source artifacts.
>
> Regards
> JB
>
-1, sadly, because:
[SHIRO-838] - Create SHA512-Hashes
They are not attached.
However, those hashes are required by the ASF (sha256 and sha512 to be
exact).
We currently have none of those attached.
François and I found out we were using an outdated version of the Apache
parent pom.
So we nee
Hi sb.
Did you set the "cipherKey" to the same value (or a value at all) on all
your instances?
See: https://shiro.apache.org/configuration.html
Also, if you have multiple servers, you'd either need to configure session
stickyness (eg via Loadbalancer and JSESSIONID) and/or a distributed
sessio
Hi!
The vote has passed with the folowing result:
+1: François Papon, Jean-Baptiste Onofré, Brian Demers, Benjamin Marwell
No vetoes had been cast.
The change will be promoted and no further integration-test- or
sample-artifacts will be deployed to central, starting with 1.9.0.
- Ben
Here's my own +1.
Am Di., 15. Feb. 2022 um 08:43 Uhr schrieb Francois Papon
:
>
> +1
>
> regards,
>
> François
>
> On 15/02/2022 08:01, Benjamin Marwell wrote:
> > Hello Shiro devs and users!
> >
> > As discussed on the dev list, there seems
Hello Shiro devs and users!
As discussed on the dev list, there seems to be a majority in favour
of not deploying integration tests and samples anymore.
The change is targeted to Shiro 2.0.0 and either Shiro 1.9.1 or 1.10.0.
It can be integrated in 1.9.0 as well if there is demand.
This vote does
Thanks, I will start a code vote on the dev and user list then! :)
Am Di., 15. Feb. 2022 um 05:15 Uhr schrieb Jean-Baptiste Onofré
:
>
> +1
>
> It sounds good to me.
>
> Regards
> JB
>
> On Mon, Feb 14, 2022 at 12:28 PM Benjamin Marwell wrote:
> >
> > Hi al
Hi all!
Looking at the deploy/upload times and the usage stats,
not deploying some of the modules might be a good idea.
We could set maven.deploy.skip=true for some modules, especially:
* integration tests
* samples
Those artifacts are usually only interesting for development (ITs) and
for refe
Hi everyone!
After we talked about technologies and settled on jbake for now a few
months ago,
we are now done with the conversion of the site from SCMS to JBake.
You can see the current tree here:
https://github.com/apache/shiro-site/tree/jbake
Please take a look at the following things:
* READM
Hi Dinakar!
So far we only changed the artifacts
(https://issues.apache.org/jira/browse/SHIRO-750) but kept the
javax-namespace. The jakarta-namespace will be introduced with a later
jakarta version (I think EE 9, if I am not mistaken).
When this happens, the best solution is to use an applicatio
Hi DInakar,
If you see something printed using System.out.println(), you are
probably already setting the attribute correctly.
It has been some time since I touched JSPs, though.
Inside your input, you need to specify the value:
${username}
/>
Please see if it works for you.
- Ben
Am Mi., 2
Hi everyone!
Which issues do we want to implement in a 1.9.0 release?
Here is my suggestion in no particular order:
* https://issues.apache.org/jira/browse/SHIRO-840
Java 17 compatibility
* https://issues.apache.org/jira/browse/SHIRO-838
Create SHA512-Hashes
* https://issues.apache.org/jira/
Same goes for:
contribute.md
how-to-contribute.md
Am Fr., 10. Sept. 2021 um 11:17 Uhr schrieb Benjamin Marwell
:
>
> Hi,
>
> we have two similar feature overview pages:
> http://shiro.apache.org/features-overview.html
> and
> http://shiro.apache.org/features.html
>
>
Hi,
we have two similar feature overview pages:
http://shiro.apache.org/features-overview.html
and
http://shiro.apache.org/features.html
Would someone be so kind as to merge them into one page (preferably
features.md, because that one is linked from the navigation)?
Thanks,
Ben
ated site to the CDN, via git)
> > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Staticwebsitecontentgeneration
> >
> >
> > Lots of thoughts, not a lot of suggestions on moving forward, sorry.
> > Of the three listed, I on
already.
On the other hand:
* probably short support tracks with yupiik minisite.
* maven plugin, so we don't even need sdkman if you don't have it already.
--
Ben
Am Mo., 30. Aug. 2021 um 13:44 Uhr schrieb Benjamin Marwell
:
>
> Hello everyone!
>
> Every now and then we h
Hello everyone!
Every now and then we have a discussion about replacing the scms site
generator which we currently use with something more popular.
There are three tools which came to our minds so far:
* hugo [1]
* jbake [2]
* yupiik minisite [3]
"hugo" is by far the most popular one next to jek
The Shiro team is pleased to announce the release of Apache Shiro version 1.8.0.
We solved three issues:
Bug
[SHIRO-678] - Strings garbled when POST without JSESSIONID cookie
[SHIRO-825] - Trailing slash in URI results in
"IllegalArgumentException: There is no configured chain under the
name
Hi,
This vote passed with the following result:
+1 (binding): Brian Demers, François Papon, Jean-Baptiste Onofré,
Benjamin Marwell
I'll finalize the release process and send the announcements soon.
Thanks all for your vote!
--
Ben
e!
> >
> > regards,
> >
> > François
> > fpa...@apache.org
> >
> > Le 23/08/2021 à 21:16, Benjamin Marwell a écrit :
> > > This is a call to vote in favor of releasing Apache Shiro version
> 1.8.0.
> > >
> > > We solved 3 issues for
[
https://issues.apache.org/jira/browse/SHIRO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-830:
---
Fix Version/s: 1.8.1
> Update aspectj-maven-plugin to 1.14.0 to support Java
This is a call to vote in favor of releasing Apache Shiro version 1.8.0.
We solved 3 issues for 1.8.0:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950&version=12350384
Bug
[SHIRO-678] - Strings garbled when POST without JSESSIONID cookie
[SHIRO-825] - Trailing slash
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-829:
---
Fix Version/s: (was: 1.8.0)
(was: 1.7.2)
> beanPostProcessor
[
https://issues.apache.org/jira/browse/SHIRO-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-769.
--
Resolution: Information Provided
Hi [~gexiuyu],
if you have any other questions, please feel
[
https://issues.apache.org/jira/browse/SHIRO-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell reassigned SHIRO-216:
--
Assignee: Benjamin Marwell
> Add @Documented to Shiro authorization annotati
[
https://issues.apache.org/jira/browse/SHIRO-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell resolved SHIRO-216.
Resolution: Fixed
> Add @Documented to Shiro authorization annotati
[
https://issues.apache.org/jira/browse/SHIRO-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-216:
---
Fix Version/s: 1.8.0
> Add @Documented to Shiro authorization annotati
[
https://issues.apache.org/jira/browse/SHIRO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-211.
--
Resolution: Won't Fix
Not used in tests anymore, see SHIRO-836.
> Rename jsecurity-sa
Benjamin Marwell created SHIRO-836:
--
Summary: Delete jsecurty-sample.jks
Key: SHIRO-836
URL: https://issues.apache.org/jira/browse/SHIRO-836
Project: Shiro
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SHIRO-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-206.
--
Resolution: Won't Fix
Closing this because of declining interest (there hasn't been
[
https://issues.apache.org/jira/browse/SHIRO-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-174.
--
Resolution: Won't Fix
With the raise of vaadin (and JavaScript frontend frameworks), th
[
https://issues.apache.org/jira/browse/SHIRO-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-165.
--
Resolution: Won't Fix
While cal10n is essentially dead, i18n support for a library is no
[
https://issues.apache.org/jira/browse/SHIRO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-134.
--
Resolution: Invalid
It seems that this has already been done.
> Combine aspectj and standal
[
https://issues.apache.org/jira/browse/SHIRO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-20.
-
Resolution: Won't Fix
Digest auth is not commonly used anymore for http authentication. I
[
https://issues.apache.org/jira/browse/SHIRO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-44.
-
Assignee: (was: Les Hazlewood)
Resolution: Won't Fix
Probably solved by current A
[
https://issues.apache.org/jira/browse/SHIRO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-26.
-
Resolution: Duplicate
Will track progress in SHIRO-337 as there is more ongoing discussion already
[
https://issues.apache.org/jira/browse/SHIRO-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-216:
---
Component/s: (was: Authorization (access control) )
Documentation
>
[
https://issues.apache.org/jira/browse/SHIRO-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-216:
---
Fix Version/s: 2.0.0
> Add @Documented to Shiro authorization annotati
[
https://issues.apache.org/jira/browse/SHIRO-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell resolved SHIRO-248.
Resolution: Fixed
Was fixed at some time in the past.
> Apache Shiro Logo link to H
[
https://issues.apache.org/jira/browse/SHIRO-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-33:
--
Component/s: Documentation
> Features overview
> -
>
>
[
https://issues.apache.org/jira/browse/SHIRO-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-71:
--
Component/s: Integration: Spring
> Using SecureRemoteInvocationFactory without a preestablis
[
https://issues.apache.org/jira/browse/SHIRO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-45:
--
Component/s: Web Site
> In the quick start guide add information about default realm, based
[
https://issues.apache.org/jira/browse/SHIRO-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-33:
--
Component/s: Web Site
> Features overview
> -
>
> K
[
https://issues.apache.org/jira/browse/SHIRO-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-629:
---
Description:
While looking at the WildcardPermission I see it allows a much wider range of
[
https://issues.apache.org/jira/browse/SHIRO-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401349#comment-17401349
]
Benjamin Marwell commented on SHIRO-629:
Hi [~pkriens],
we believe the
[
https://issues.apache.org/jira/browse/SHIRO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-815.
--
Resolution: Invalid
Hi [~spadarthi]
I am closing this as invalid because it has not been
[
https://issues.apache.org/jira/browse/SHIRO-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-826:
---
Labels: question (was: )
> HTTP 400 with encoded umlauts in
[
https://issues.apache.org/jira/browse/SHIRO-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-826.
--
Resolution: Not A Bug
> HTTP 400 with encoded umlauts in
[
https://issues.apache.org/jira/browse/SHIRO-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401133#comment-17401133
]
Benjamin Marwell commented on SHIRO-206:
[~bdemers] is this still on main o
[
https://issues.apache.org/jira/browse/SHIRO-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-261:
---
Priority: Minor (was: Major)
> Simplify Contribute P
[
https://issues.apache.org/jira/browse/SHIRO-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401129#comment-17401129
]
Benjamin Marwell commented on SHIRO-629:
Hi [~pkriens], thanks for repor
[
https://issues.apache.org/jira/browse/SHIRO-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-769:
---
Labels: stale (was: )
> Multiple realm exceptions cannot be ca
[
https://issues.apache.org/jira/browse/SHIRO-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401122#comment-17401122
]
Benjamin Marwell commented on SHIRO-769:
Hi [~gexiuyu]. Please kindly report
[
https://issues.apache.org/jira/browse/SHIRO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-572:
---
Fix Version/s: 2.0.0
> Validate everything in 1.2 / 1.3 has merged into
[
https://issues.apache.org/jira/browse/SHIRO-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell resolved SHIRO-825.
Resolution: Fixed
> Trailing slash in URI results in "IllegalArgumentException: The
[
https://issues.apache.org/jira/browse/SHIRO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-678.
--
Resolution: Fixed
> Strings garbled when POST without JSESSIONID coo
[
https://issues.apache.org/jira/browse/SHIRO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400975#comment-17400975
]
Benjamin Marwell commented on SHIRO-678:
merged and cherry-picked into 1
[
https://issues.apache.org/jira/browse/SHIRO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-678:
---
Fix Version/s: 1.8.0
2.0.0
> Strings garbled when POST without JSESSIO
[
https://issues.apache.org/jira/browse/SHIRO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell reassigned SHIRO-678:
--
Assignee: Benjamin Marwell
> Strings garbled when POST without JSESSIONID coo
Benjamin Marwell created SHIRO-830:
--
Summary: Update aspectj-maven-plugin to 1.14.0 to support Java 16
Key: SHIRO-830
URL: https://issues.apache.org/jira/browse/SHIRO-830
Project: Shiro
[
https://issues.apache.org/jira/browse/SHIRO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-678:
---
Affects Version/s: 1.7.1
> Strings garbled when POST without JSESSIONID coo
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393707#comment-17393707
]
Benjamin Marwell commented on SHIRO-829:
Hi [~xcz],
it is actually my mis
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393702#comment-17393702
]
Benjamin Marwell commented on SHIRO-829:
I will check the pro
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393698#comment-17393698
]
Benjamin Marwell commented on SHIRO-829:
Oh sorry, I totally overlooked you
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393694#comment-17393694
]
Benjamin Marwell commented on SHIRO-829:
Well, it got a little better it s
[
https://issues.apache.org/jira/browse/SHIRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393644#comment-17393644
]
Benjamin Marwell commented on SHIRO-829:
There is something wrong: why is
Benjamin Marwell created SHIRO-828:
--
Summary: aspectj-maven-plugin 1.40.0
Key: SHIRO-828
URL: https://issues.apache.org/jira/browse/SHIRO-828
Project: Shiro
Issue Type: Dependency upgrade
che/shiro-labs` git repo to test out
> ideas for things that are NOT ready for the main tree. (Maven does
> something similar with https://github.com/apache/maven-studies/)
>
> On Sun, Aug 1, 2021 at 4:00 PM Benjamin Marwell wrote:
>
> > Hi everyone,
> >
> > we had
[
https://issues.apache.org/jira/browse/SHIRO-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-206:
---
Fix Version/s: (was: 2.0.0)
> Support for JSF/Facel
1 - 100 of 282 matches
Mail list logo
