[
https://issues.apache.org/jira/browse/SHIRO-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell closed SHIRO-468.
--
Assignee: Benjamin Marwell
Resolution: Information Provided
> How to use multiple logins
[
https://issues.apache.org/jira/browse/SHIRO-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104570#comment-17104570
]
Francois Papon commented on SHIRO-468:
--
[~bmarwell] can be closed, it's a very old issue and no
[
https://issues.apache.org/jira/browse/SHIRO-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell resolved SHIRO-774.
Resolution: Fixed
> Remove wrong usage of prerequisites in pom.xml
>
Benjamin Marwell created SHIRO-777:
--
Summary: Remove PowerMock and update the enforcer exclusion list
Key: SHIRO-777
URL: https://issues.apache.org/jira/browse/SHIRO-777
Project: Shiro
Benjamin Marwell created SHIRO-776:
--
Summary: JUnit update to version 5
Key: SHIRO-776
URL: https://issues.apache.org/jira/browse/SHIRO-776
Project: Shiro
Issue Type: Test
+1 to use unique mocking framework as possible.
regards,
François
fpa...@apache.org
Le 11/05/2020 à 11:29, Benjamin Marwell a écrit :
> PowerMock has the goal to make final classes mockable (which will stop
> working in future java versions and is an antipattern).
> This means they have
PowerMock has the goal to make final classes mockable (which will stop
working in future java versions and is an antipattern).
This means they have different goals and cannot be userd interchangeably.
But +1 to remove PowerMock at this point and use EasyMock as long as
it serves us well.
Am Mo.,
[
https://issues.apache.org/jira/browse/SHIRO-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell reassigned SHIRO-774:
--
Assignee: Benjamin Marwell
> Remove wrong usage of prerequisites in pom.xml
>
Something helpful would be to use an unique mocking framework. So maybe
removing powermock to use easymock only.
Thoughts ?
Regards
JB
> Le 11 mai 2020 à 11:12, Benjamin Marwell a écrit :
>
> As EasyMock is used throughout the code, I changed my mind about this
> topic and would like to keep
As EasyMock is used throughout the code, I changed my mind about this
topic and would like to keep it.
I see no imminent reason to change existing (test) code.
However, I am open whether to use Mockito for new tests or not, see
maven link and rationale from the first e-mail.
At the moment, there
[
https://issues.apache.org/jira/browse/SHIRO-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell reassigned SHIRO-551:
--
Assignee: Benjamin Marwell
> DelegatingSubject should implement toString()
>
[
https://issues.apache.org/jira/browse/SHIRO-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon reassigned SHIRO-750:
Assignee: Benjamin Marwell
> Migrate to jakarta APIs
> ---
>
>
[
https://issues.apache.org/jira/browse/SHIRO-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon reassigned SHIRO-773:
Assignee: Benjamin Marwell
> Outdated Groovy version does not work with JDK14
>
[
https://issues.apache.org/jira/browse/SHIRO-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon reassigned SHIRO-772:
Assignee: Benjamin Marwell
> PowerMock blocks JDK 11+ builds
>
[
https://issues.apache.org/jira/browse/SHIRO-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Papon resolved SHIRO-771.
--
Assignee: Benjamin Marwell
Resolution: Resolved
> Add OpenJDK-OpenJ9 travis builds
>
15 matches
Mail list logo
