Fix javadoc errors and warnings

Resolves #1624

spring-batch-integration/src/main/java/org/springframework/batch/integration/async/AsyncItemProcessor.java

@@ -33,11 +33,12 @@ import org.springframework.util.Assert;
  * An {@link ItemProcessor} that delegates to a nested processor and in the background. To
  * allow for background processing the return value from the processor is a {@link Future}
  * which needs to be unpacked before the item can be used by a client.
- *
+ * <p>
  * Because the {@link Future} is typically unwrapped in the {@link ItemWriter}, there are
  * lifecycle and stats limitations (since the framework doesn't know what the result of
  * the processor is). While not an exhaustive list, things like
- * {@link StepExecution#filterCount} will not reflect the number of filtered items and
+ * {@link StepExecution#getFilterCount()} will not reflect the number of filtered items
+ * and
  * {@link org.springframework.batch.core.ItemProcessListener#onProcessError(Object, Exception)}
  * will not be called.
  *

spring-batch-integration/src/main/java/org/springframework/batch/integration/chunk/RemoteChunkingManagerStepBuilder.java

@@ -363,7 +363,7 @@ public class RemoteChunkingManagerStepBuilder<I, O> extends FaultTolerantStepBui
 	 * This method will throw a {@link UnsupportedOperationException} since the item
 	 * writer of the manager step in a remote chunking setup will be automatically set to
 	 * an instance of {@link ChunkMessageChannelItemWriter}.
-	 *
+	 * <p>
 	 * When building a manager step for remote chunking, no item writer must be provided.
 	 * @throws UnsupportedOperationException if an item writer is provided
 	 * @see ChunkMessageChannelItemWriter

spring-batch-integration/src/main/java/org/springframework/batch/integration/partition/MessageChannelPartitionHandler.java

@@ -64,7 +64,7 @@ import org.springframework.util.CollectionUtils;
  * pick up missing messages and processing. The remote workers need access to the Spring
  * Batch {@link JobRepository} so that the shared state across those restarts can be
  * managed centrally.
- *
+ * <p>
  * While a {@link org.springframework.messaging.MessageChannel} is used for sending the
  * requests to the workers, the worker's responses can be obtained in one of two ways:
  * <ul>

spring-batch-integration/src/main/java/org/springframework/batch/integration/partition/RemotePartitioningManagerStepBuilder.java

@@ -306,7 +306,7 @@ public class RemotePartitioningManagerStepBuilder extends PartitionStepBuilder {
 	 * This method will throw a {@link UnsupportedOperationException} since the partition
 	 * handler of the manager step will be automatically set to an instance of
 	 * {@link MessageChannelPartitionHandler}.
-	 *
+	 * <p>
 	 * When building a manager step for remote partitioning using this builder, no
 	 * partition handler must be provided.
 	 * @param partitionHandler a partition handler

spring-batch-integration/src/test/java/org/springframework/batch/integration/StepSupport.java

@@ -31,7 +31,7 @@ public class StepSupport implements Step {
 	private int startLimit = 1;
 
 	/**
-	 * @param name
+	 * @param name the step name
 	 */
 	public StepSupport(String name) {
 		super();