From beba702180111d10bc54058f0ec43fb323eb8c01 Mon Sep 17 00:00:00 2001
From: "Jesse N. Glick" <jglick@apache.org>
Date: Thu, 2 Dec 2004 22:06:15 +0000
Subject: [PATCH] Trivial Javadoc formatting edits.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@277113 13f79535-47bb-0310-9956-ffa450edef68
---
 .../apache/tools/ant/taskdefs/ImportTask.java   | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/src/main/org/apache/tools/ant/taskdefs/ImportTask.java b/src/main/org/apache/tools/ant/taskdefs/ImportTask.java
index 99b9e65e9..a06ee78e0 100644
--- a/src/main/org/apache/tools/ant/taskdefs/ImportTask.java
+++ b/src/main/org/apache/tools/ant/taskdefs/ImportTask.java
@@ -29,27 +29,26 @@ import java.io.IOException;
 import java.util.Vector;
 
 /**
- * <p>
  * Task to import another build file into the current project.
  * <p>
  * It must be 'top level'. On execution it will read another Ant file
  * into the same Project.
+ * </p>
  * <p>
  * <b>Important</b>: we have not finalized how relative file references
- * will be resolved in deep/complex build hierarchies -such as what happens
+ * will be resolved in deep/complex build hierarchies - such as what happens
  * when an imported file imports another file. Use absolute references for
  * enhanced build file stability, especially in the imported files.
- *
- * Examples
+ * </p>
+ * <p>Examples:</p>
  * <pre>
- * &lt;import file="../common-targets.xml" /&gt;
+ * &lt;import file="../common-targets.xml"/&gt;
  * </pre>
- * Import targets from a file in a parent directory.
- *<p>
+ * <p>Import targets from a file in a parent directory.</p>
  * <pre>
- * &lt;import file="${deploy-platform}.xml" /&gt;
+ * &lt;import file="${deploy-platform}.xml"/&gt;
  * </pre>
- * Import the project defined by the property deploy-platform
+ * <p>Import the project defined by the property <code>deploy-platform</code>.</p>
  *
  * @since Ant1.6
  * @ant.task category="control"