Author: reschke
Date: Sat Jan  7 14:33:34 2017
New Revision: 1777797

URL: http://svn.apache.org/viewvc?rev=1777797&view=rev
Log:
OAK-5328: JDK18 doctool compliance - broken paragraph tags

Modified:
    
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/MultiplexingNodeStore.java
    
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/package-info.java

Modified: 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/MultiplexingNodeStore.java
URL: 
http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/MultiplexingNodeStore.java?rev=1777797&r1=1777796&r2=1777797&view=diff
==============================================================================
--- 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/MultiplexingNodeStore.java
 (original)
+++ 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/MultiplexingNodeStore.java
 Sat Jan  7 14:33:34 2017
@@ -63,13 +63,13 @@ import static com.google.common.collect.
  *   <li>Many JCR subsystems require global state, e.g. the versioning store. 
This global state
  *   can become corrupt if multiple mounts operate on it or if mounts are 
added and removed.</li>
  * </ol>
- *
- * As such, the only supported configuration is at most a single write-enabled 
store.</p>
+ * 
+ * <p>As such, the only supported configuration is at most a single 
write-enabled store.
  *
  * <p>Because of the limitation described above, right now the only correct 
way to use
  * MultiplexingNodeStore is to create a normal repository, split it into parts
  * using oak-upgrade {@code --{include,exclude}-paths} and then configure this
- * node store implementation to multiplex split parts together.</p>
+ * node store implementation to multiplex split parts together.
  */
 public class MultiplexingNodeStore implements NodeStore, Observable {
 

Modified: 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/package-info.java
URL: 
http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/package-info.java?rev=1777797&r1=1777796&r2=1777797&view=diff
==============================================================================
--- 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/package-info.java
 (original)
+++ 
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/multiplex/package-info.java
 Sat Jan  7 14:33:34 2017
@@ -20,7 +20,6 @@
  * <p>This package contains support classes for implementing a multiplexed 
persistence at the {@linkplain org.apache.jackrabbit.oak.spi.state.NodeStore} 
level.</p>
  *
  * <h2>Design goals</h2>
- * <p>
  * <ol>
  *   <li>Transparency of the multiplexing setup. Neither the NodeStores nor 
the code using a multiplexed
  *       NodeStore should be aware of the specific implementation being 
used.</li>
@@ -28,34 +27,33 @@
  *       NodeStore implementation.</li>
  *   <li>Negligible performance impact. Multiplexing should not add a 
significat performance overhead.</li>
  * </ol>
- * </p>
  *
  * <h2>Implementation</h2>
  *
  * <p>The main entry point is the {@link 
org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingNodeStore},
- * which wraps one or more NodeStore instances. Also of interest are the 
{@link org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingNodeState} and 
{@link org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingNodeBuilder}.</p>
+ * which wraps one or more NodeStore instances. Also of interest are the 
{@link org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingNodeState} and 
{@link org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingNodeBuilder}.
  *
- * <p> These classes maintain internal mappings of the 'native' objects. For 
instance, if the
+ * <p>These classes maintain internal mappings of the 'native' objects. For 
instance, if the
  * multiplexing NodeStore holds two MemoryNodeStore instances, then a call to 
{@linkplain org.apache.jackrabbit.oak.spi.state.NodeStore#getRoot()}
  * will return a multiplexing NodeState backed by two MemoryNodeState 
instances. Similarly, a call to {@linkplain 
org.apache.jackrabbit.oak.spi.state.NodeState#builder()} will return a 
multiplexing
- * NodeBuilder backed by two MemoryNodeState instances.</p>
+ * NodeBuilder backed by two MemoryNodeState instances.
  *
  * <p>Using this approach allows us to always keep related NodeStore, 
NodeState and NodeBuilder
- * instances isolated from other instances.</p>
+ * instances isolated from other instances.
  *
  * <h2>Open items</h2>
  *
- * <p>1. Brute-force support for oak:mount nodes.</p>
+ * <p>1. Brute-force support for oak:mount nodes.
  *
  *  <p>The {@link 
org.apache.jackrabbit.oak.spi.mount.Mount#getPathFragmentName()} method defines
  *  a name pattern that can be used by mounted stores to contribute to a patch 
which is not
  *  owned by them. For instance, a mount named <em>apps</em> which owns 
<tt>/libs,/apps</tt>
  *  can own another subtree anywhere in the repository given that a node named 
<tt>:oak-mount-apps</tt>
- *  is found.</p>
+ *  is found.
  *
  *  <p>The current implementation naively queries all stores whenever the 
child node list is prepared.
- *  This is obviously correct but may be slow.</p>
- *  {@link 
org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingContext#getContributingStores(java.lang.String,
 com.google.common.base.Function)}</p>
+ *  This is obviously correct but may be slow.
+ *  {@link 
org.apache.jackrabbit.oak.plugins.multiplex.MultiplexingContext#getContributingStores(java.lang.String,
 com.google.common.base.Function)}
  */
 package org.apache.jackrabbit.oak.plugins.multiplex;
 


Reply via email to