This is an automated email from the ASF dual-hosted git repository.
fpapon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shiro.git
The following commit(s) were added to refs/heads/master by this push:
new 136198c fix typo in javadoc for Permission
new 677fbb8 Merge pull request #117 from
ThomasVitale/correct_permission_javadoc
136198c is described below
commit 136198c23f81e5deada7aa904831e065b575538c
Author: Thomas Vitale <[email protected]>
AuthorDate: Sat Feb 9 01:25:31 2019 +0100
fix typo in javadoc for Permission
---
core/src/main/java/org/apache/shiro/authz/Permission.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/core/src/main/java/org/apache/shiro/authz/Permission.java
b/core/src/main/java/org/apache/shiro/authz/Permission.java
index ab7082f..d8728ff 100644
--- a/core/src/main/java/org/apache/shiro/authz/Permission.java
+++ b/core/src/main/java/org/apache/shiro/authz/Permission.java
@@ -32,7 +32,7 @@ package org.apache.shiro.authz;
* <em>User</em> or <em>Guest</em> roles, etc.
* <p/>
* But if you have a dynamic security model, where roles can be created and
deleted at runtime, you can't hard-code
- * role names in your code. In this environment, roles themselves aren't
aren't very useful. What matters is what
+ * role names in your code. In this environment, roles themselves aren't very
useful. What matters is what
* <em>permissions</em> are assigned to these roles.
* <p/>
* Under this paradigm, permissions are immutable and reflect an application's
raw functionality
