You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by oh...@apache.org on 2015/05/16 19:47:32 UTC
svn commit: r1679787 -
/commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java
Author: oheger
Date: Sat May 16 17:47:32 2015
New Revision: 1679787
URL: http://svn.apache.org/r1679787
Log:
Javadoc errors: Incorrect nesting of <p> tags.
Modified:
commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java
Modified: commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java
URL: http://svn.apache.org/viewvc/commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java?rev=1679787&r1=1679786&r2=1679787&view=diff
==============================================================================
--- commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java (original)
+++ commons/proper/configuration/trunk/src/main/java/org/apache/commons/configuration2/io/FileHandler.java Sat May 16 17:47:32 2015
@@ -52,6 +52,7 @@ import org.apache.commons.logging.LogFac
* manage is passed in. Basically, this object is assigned a location from which
* it is loaded and to which it can be saved. The following possibilities exist
* to specify such a location:
+ * </p>
* <ul>
* <li>URLs: With the method {@code setURL()} a full URL to the configuration
* source can be specified. This is the most flexible way. Note that the
@@ -66,7 +67,6 @@ import org.apache.commons.logging.LogFac
* {@code setBasePath()} method. The file name, non surprisingly, defines the
* name of the configuration file.</li>
* </ul>
- * </p>
* <p>
* An instance stores a location. The {@code load()} and {@code save()} methods
* that do not take an argument make use of this internal location.
@@ -84,6 +84,7 @@ import org.apache.commons.logging.LogFac
* exist. So there may be some differences in the way location information is
* interpreted by load and save operations. In order to avoid this, the
* following approach is recommended:
+ * </p>
* <ul>
* <li>Use the desired {@code setXXX()} methods to define the location of the
* file to be loaded.</li>
@@ -92,11 +93,11 @@ import org.apache.commons.logging.LogFac
* <li>Later on, {@code save()} can be called. This method now has sufficient
* information to store the file at the correct location.</li>
* </ul>
- * </p>
* <p>
* When loading or saving a {@code FileBased} object some additional
* functionality is performed if the object implements one of the following
* interfaces:
+ * </p>
* <ul>
* <li>{@code FileLocatorAware}: In this case an object with the current file
* location is injected before the load or save operation is executed. This is
@@ -109,7 +110,6 @@ import org.apache.commons.logging.LogFac
* object it is not allowed to perform multiple save operations in parallel;
* therefore, by obtaining a write lock, we are on the safe side.)</li>
* </ul>
- * </p>
* <p>
* This class is thread-safe.
* </p>