Java: Fix documentation format and indentation

Modules/UseJava.cmake

@@ -3,8 +3,6 @@
 # has already been loaded.  See FindJava.cmake for information on how to
 # load Java into your CMake project.
 #
-# Available Functions:
-#
 # add_jar(TARGET_NAME SRC1 SRC2 .. SRCN RCS1 RCS2 .. RCSN)
 #
 # This command creates a <TARGET_NAME>.jar. It compiles the given source
@@ -70,8 +68,7 @@
 #   CLASS_DIR          The directory where the class files can be found. For
 #                      example to use them with javah.
 #
-#   find_jar(
-#            <VAR>
+# find_jar(<VAR>
 #          name | NAMES name1 [name2 ...]
 #          [PATHS path1 [path2 ... ENV var]]
 #          [VERSIONS version1 [version2]]
@@ -103,16 +100,7 @@
 # DESTINATION. It should be called in the same scope as add_jar()
 # or it will fail.
 #
-#   create_javadoc
-#
-#     Create jave documentation based on files or packages. For more
-#     details please read the javadoc manpage.
-#
-#     There are two main signatures for create_javadoc. The first
-#     signature works with package names on a path with source files:
-#
-#     create_javadoc(
-#                    <VAR>
+# create_javadoc(<VAR>
 #                PACKAGES pkg1 [pkg2 ...]
 #                [SOURCEPATH <sourcepath>]
 #                [CLASSPATH <classpath>]
@@ -124,6 +112,12 @@
 #                [VERSION TRUE|FALSE]
 #               )
 #
+# Create jave documentation based on files or packages. For more
+# details please read the javadoc manpage.
+#
+# There are two main signatures for create_javadoc. The first
+# signature works with package names on a path with source files:
+#
 #   Example:
 #   create_javadoc(my_example_doc
 #     PACKAGES com.exmaple.foo com.example.bar
@@ -139,8 +133,7 @@
 # The second signature for create_javadoc works on a given list of
 # files.
 #
-#     create_javadoc(
-#                    <VAR>
+#   create_javadoc(<VAR>
 #                  FILES file1 [file2 ...]
 #                  [CLASSPATH <classpath>]
 #                  [INSTALLPATH <install path>]