This is an automated email from the ASF dual-hosted git repository.
reschke pushed a commit to branch OAK-11650
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git
The following commit(s) were added to refs/heads/OAK-11650 by this push:
new 16dbc93745 OAK-11650: Fix Javadoc errors - > as a list marker
16dbc93745 is described below
commit 16dbc93745c4a4fc30dd3e690b2901cba625c5e6
Author: Julian Reschke <[email protected]>
AuthorDate: Thu Apr 10 10:57:14 2025 +0100
OAK-11650: Fix Javadoc errors - > as a list marker
---
.../composite/CompositeProviderScopeTest.java | 4 ++--
.../authentication/L3_LoginModuleTest.java | 6 +++---
.../advanced/L2_SetupAggregationTest.java | 24 +++++++++++-----------
.../advanced/L3_UnderstandAggregationTest.java | 10 ++++-----
.../security/principal/L3_EveryoneTest.java | 8 ++++----
.../principal/L4_PrincipalProviderTest.java | 6 +++---
.../user/L10_RemovalAndMembershipTest.java | 4 ++--
.../exercise/security/user/L8_MembershipTest.java | 4 ++--
8 files changed, 33 insertions(+), 33 deletions(-)
diff --git
a/oak-core/src/test/java/org/apache/jackrabbit/oak/security/authorization/composite/CompositeProviderScopeTest.java
b/oak-core/src/test/java/org/apache/jackrabbit/oak/security/authorization/composite/CompositeProviderScopeTest.java
index 6b071c8c77..f82b5286a1 100644
---
a/oak-core/src/test/java/org/apache/jackrabbit/oak/security/authorization/composite/CompositeProviderScopeTest.java
+++
b/oak-core/src/test/java/org/apache/jackrabbit/oak/security/authorization/composite/CompositeProviderScopeTest.java
@@ -45,8 +45,8 @@ import static org.junit.Assert.assertTrue;
*
* - default permission provider
* - custom provider that
- * > supports namespace-management and nodetype-def-mgt permission on
repository level
- * > write permission below {@link #TEST_A_PATH}.
+ * + supports namespace-management and nodetype-def-mgt permission on
repository level
+ * + write permission below {@link #TEST_A_PATH}.
*
* The tests are executed both for the set of principals associated with the
test
* user and with the admin session.
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authentication/L3_LoginModuleTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authentication/L3_LoginModuleTest.java
index 3a3a1fd02e..e963d2c83f 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authentication/L3_LoginModuleTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authentication/L3_LoginModuleTest.java
@@ -54,9 +54,9 @@ import org.junit.Test;
* {@link #getConfiguration()} method.
* Change the JAAS configuration and use the {@link #testLogin()} method to
* walk through the login. For example
- * > look at ConfigurationUtil for various options
- * > manually create a different configuration with different control flags
- * > create a configuration that also includes the {@link CustomLoginModule}
+ * + look at ConfigurationUtil for various options
+ * + manually create a different configuration with different control flags
+ * + create a configuration that also includes the {@link CustomLoginModule}
* Discuss your findings
*
*
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L2_SetupAggregationTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L2_SetupAggregationTest.java
index da388cb708..659f51ca7c 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L2_SetupAggregationTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L2_SetupAggregationTest.java
@@ -37,22 +37,22 @@ package
org.apache.jackrabbit.oak.exercise.security.authorization.advanced;
* and deploy it with your OSGi based Oak setup.
*
* Hint: Oak comes with 2 additional authorization models, which you can use
- * > Closed User Groups in oak-authorization-cug (see also
http://jackrabbit.apache.org/oak/docs/security/authorization/cug.html)
- * > Read Only in oak-exercise
+ * + Closed User Groups in oak-authorization-cug (see also
http://jackrabbit.apache.org/oak/docs/security/authorization/cug.html)
+ * + Read Only in oak-exercise
*
* Questions:
- * > Can you identify the OSGi components that come with the model?
- * > Does your model require any mandatory configuration in order to be
functional?
+ * + Can you identify the OSGi components that come with the model?
+ * + Does your model require any mandatory configuration in order to be
functional?
*
* - Adjust Configuration of 'Apache Jackrabbit Oak SecurityProvider'
* In a second step you should adjust the configuration of the
SecurityProvider
* in order to make sure the additional AuthorizationConfiguration is
properly
* wired with the security setup.
*
- * > Add the addition configuration to the list of required service IDs (see
also http://jackrabbit.apache.org/oak/docs/security/introduction.html)
- * > Check the value of 'Authorization Composition Type'.
- * > Observe the log INFOs to verify the SecurityProvider is properly
registered
- * > Inspect the references to 'authorizationConfiguration' in
org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration
+ * + Add the addition configuration to the list of required service IDs (see
also http://jackrabbit.apache.org/oak/docs/security/introduction.html)
+ * + Check the value of 'Authorization Composition Type'.
+ * + Observe the log INFOs to verify the SecurityProvider is properly
registered
+ * + Inspect the references to 'authorizationConfiguration' in
org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration
* and verify that the extra module shows up there.
*
* - Verify Access Control Management and Permission Evaluation
@@ -66,10 +66,10 @@ package
org.apache.jackrabbit.oak.exercise.security.authorization.advanced;
* - Play with the configuration option 'Authorization Composition Type'.
*
* Questions:
- * > Would it be an option to use "OR" as the composition type with the
setup you chose?
- * > What would be the result if this was a valid option?
- * > If it was a valid option, imaging a setup scenario where it would not
work.
- * > If it wasn't an option, explain why. Think about a scenario where it
was valid.
+ * + Would it be an option to use "OR" as the composition type with the
setup you chose?
+ * + What would be the result if this was a valid option?
+ * + If it was a valid option, imaging a setup scenario where it would not
work.
+ * + If it wasn't an option, explain why. Think about a scenario where it
was valid.
*
* </pre>
*/
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L3_UnderstandAggregationTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L3_UnderstandAggregationTest.java
index 42c82d831f..8b9e1b583f 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L3_UnderstandAggregationTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/authorization/advanced/L3_UnderstandAggregationTest.java
@@ -82,11 +82,11 @@ import static org.junit.Assert.assertTrue;
*
* - Write more tests to explore aggregation of additional features within the
* authorization setup such as e.g.
- * > Privilege discovery
- * > Repository level privileges such as e.g. ability to register a new node
type.
- * > XML Import
- * > Validation
- * > Repository Initialization
+ * + Privilege discovery
+ * + Repository level privileges such as e.g. ability to register a new node
type.
+ * + XML Import
+ * + Validation
+ * + Repository Initialization
*
*
* Advanced Exercises
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L3_EveryoneTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L3_EveryoneTest.java
index 7978518231..a058d7b9ed 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L3_EveryoneTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L3_EveryoneTest.java
@@ -65,10 +65,10 @@ import org.apache.jackrabbit.test.AbstractJCRTest;
* - {@link #testEveryoneAsAuthorizableGroup()}
* Additional test illustrating that the dynamic nature of the everyone
principal
* does not change if there exists a corresponding authorizable group.
- * > Create a new authorizable that corresponds to the everyone principal
(Q: what parameters are constants?)
- * > Verify that principal exposed by the authorizable corresponds to the
everyone principal.
- * > Assert that the dynamic nature of the principal has not changed.
- * > Test if the dynamic nature also applies to the authorizable
+ * + Create a new authorizable that corresponds to the everyone principal
(Q: what parameters are constants?)
+ * + Verify that principal exposed by the authorizable corresponds to the
everyone principal.
+ * + Assert that the dynamic nature of the principal has not changed.
+ * + Test if the dynamic nature also applies to the authorizable
*
*
* Additional Exercises:
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L4_PrincipalProviderTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L4_PrincipalProviderTest.java
index 1fc86b249f..56e692ed07 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L4_PrincipalProviderTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/principal/L4_PrincipalProviderTest.java
@@ -64,9 +64,9 @@ import org.junit.Test;
* - Complete the {@link CustomPrincipalProvider}
* stub and deploy the exercise bundle in a Sling base repository
installation
* (e.g. Cq|Granite).
- * > Try to identify the tools that allow you to explore your custom
principals
- * > Play with the dynamic group membership as you define it in the
principal provider and verify that the subjects calculated upon login are
correct
- * > Play with the authorization part of the principal management
granting/revoking access for one of your custom principals
+ * + Try to identify the tools that allow you to explore your custom
principals
+ * + Play with the dynamic group membership as you define it in the
principal provider and verify that the subjects calculated upon login are
correct
+ * + Play with the authorization part of the principal management
granting/revoking access for one of your custom principals
* </pre>
*
* @see org.apache.jackrabbit.oak.spi.security.principal.PrincipalProvider
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L10_RemovalAndMembershipTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L10_RemovalAndMembershipTest.java
index 49639036ce..ec5ed28fdb 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L10_RemovalAndMembershipTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L10_RemovalAndMembershipTest.java
@@ -80,8 +80,8 @@ import static org.junit.Assert.assertTrue;
* it and verify and if members-list at 'administrators' has been adjust
(test-user removed).
*
* - Explain the result both for the main and variant.
- * > the removal failed: explain why?
- * > the member-cleanup didn't succeed: explain why?
+ * + the removal failed: explain why?
+ * + the member-cleanup didn't succeed: explain why?
*
* 4. Test Execution with 'admin'
*
diff --git
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L8_MembershipTest.java
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L8_MembershipTest.java
index b7029da8a3..9147ecf0ce 100644
---
a/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L8_MembershipTest.java
+++
b/oak-exercise/src/test/java/org/apache/jackrabbit/oak/exercise/security/user/L8_MembershipTest.java
@@ -83,8 +83,8 @@ import static org.junit.Assert.assertTrue;
* In order to complete this exercise look at the built-in node types and
* identify those types that deal with group membership.
* Once you are familiar with the node type definitions look at
- * > {@link org.apache.jackrabbit.oak.security.user.MembershipProvider} and
- * > {@link org.apache.jackrabbit.oak.security.user.MembershipWriter}
+ * + {@link org.apache.jackrabbit.oak.security.user.MembershipProvider} and
+ * + {@link org.apache.jackrabbit.oak.security.user.MembershipWriter}
* and how they deal with massive amount of members on a given group.
* Finally fix the test case :-)
*
