Checkstyle Results - Apache Log4j Flume NG Bridge

Checkstyle Results

The following document contains the results of Checkstyle.

Summary

Files	Infos	Warnings	Errors
13	0	0	23

Files

Files	I	W	E
org/apache/logging/log4j/flume/appender/FlumeAppender.java	0	0	8
org/apache/logging/log4j/flume/appender/FlumeAvroManager.java	0	0	5
org/apache/logging/log4j/flume/appender/FlumeEmbeddedManager.java	0	0	1
org/apache/logging/log4j/flume/appender/FlumeEvent.java	0	0	1
org/apache/logging/log4j/flume/appender/FlumePersistentManager.java	0	0	8

Details

org/apache/logging/log4j/flume/appender/FlumeAppender.java

Violation	Message	Line
	Type Javadoc comment is missing an @param <T> tag.	36
	Missing a Javadoc comment.	53
	Expected @param tag for '<S>'.	140
	More than 15 parameters.	140
	Line is longer than 120 characters.	173
	'60000' is a magic number.	194
	'}' is not preceded with whitespace.	197
	'cast' is not followed by whitespace.	198

org/apache/logging/log4j/flume/appender/FlumeAvroManager.java

Violation	Message	Line
	Expected @param tag for 'retries'.	79
	Expected @param tag for 'connectTimeout'.	79
	Expected @param tag for 'requestTimeout'.	79
	'1000' is a magic number.	201
	'1000' is a magic number.	204

org/apache/logging/log4j/flume/appender/FlumeEmbeddedManager.java

Violation	Message	Line
	Name 'FiLE_SEP' must match pattern '^[A-Z][A-Z0-9](_[A-Z0-9]+)$\|^capabilities$\|^log$'.	42

org/apache/logging/log4j/flume/appender/FlumeEvent.java

Violation	Message	Line
	Variable access definition in wrong order.	57

org/apache/logging/log4j/flume/appender/FlumePersistentManager.java

Violation	Message	Line
	Missing a Javadoc comment.	56
	Expected @param tag for 'properties'.	103
	Expected @param tag for 'retries'.	104
	Expected @param tag for 'connectionTimeout'.	104
	Expected @param tag for 'requestTimeout'.	105
	Expected @param tag for 'delay'.	105
	Expected @param tag for 'dataDir'.	105
	Missing a Javadoc comment.	305