Author: reschke
Date: Tue Apr 30 09:46:34 2019
New Revision: 1858415

URL: http://svn.apache.org/viewvc?rev=1858415&view=rev
Log:
OAK-8288: fix javadoc:javadoc for jdk >= 13

Modified:
    
jackrabbit/oak/trunk/oak-store-composite/src/main/java/org/apache/jackrabbit/oak/composite/package-info.java

Modified: 
jackrabbit/oak/trunk/oak-store-composite/src/main/java/org/apache/jackrabbit/oak/composite/package-info.java
URL: 
http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-store-composite/src/main/java/org/apache/jackrabbit/oak/composite/package-info.java?rev=1858415&r1=1858414&r2=1858415&view=diff
==============================================================================
--- 
jackrabbit/oak/trunk/oak-store-composite/src/main/java/org/apache/jackrabbit/oak/composite/package-info.java
 (original)
+++ 
jackrabbit/oak/trunk/oak-store-composite/src/main/java/org/apache/jackrabbit/oak/composite/package-info.java
 Tue Apr 30 09:46:34 2019
@@ -15,11 +15,11 @@
  * limitations under the License.
  */
 /**
- * <h1>Composition support</h1>
+ * <h2>Composition support</h2>
  *
  * <p>This package contains support classes for implementing a composite 
persistence at the {@linkplain org.apache.jackrabbit.oak.spi.state.NodeStore} 
level.</p>
  *
- * <h2>Design goals</h2>
+ * <h3>Design goals</h3>
  * <ol>
  *   <li>Transparency of the composition setup. Neither the NodeStores nor the 
code using a composite
  *       NodeStore should be aware of the specific implementation being 
used.</li>
@@ -28,7 +28,7 @@
  *   <li>Negligible performance impact. Composition should not add a 
significat performance overhead.</li>
  * </ol>
  *
- * <h2>Implementation</h2>
+ * <h3>Implementation</h3>
  *
  * <p>The main entry point is the {@link 
org.apache.jackrabbit.oak.composite.CompositeNodeStore},
  * which wraps one or more NodeStore instances. Also of interest are the 
{@link org.apache.jackrabbit.oak.composite.CompositeNodeState} and {@link 
org.apache.jackrabbit.oak.composite.CompositeNodeBuilder}.
@@ -41,7 +41,7 @@
  * <p>Using this approach allows us to always keep related NodeStore, 
NodeState and NodeBuilder
  * instances isolated from other instances.
  *
- * <h2>Open items</h2>
+ * <h3>Open items</h3>
  *
  * <p>1. Brute-force support for oak:mount nodes.
  *


Reply via email to