Allow SizeAndTimeBasedFNATP subclasses to provide a custom ArchiveRemover
LOGBACK-466

Documentation: Fix syntax issue with GEventEvaluator example in filters documentation.
Documentation: Fix typos in site and manual
Merge pull request #166 from ericdahl/doc-evaluatorfilter

LOGBACK-466 Documentation: Fix syntax issues with GEventEvaluator example
Merge pull request #167 from ericdahl/site-typos

Documentation: Fix typos in site and manual
Update release notes for 1.1.0

Add note for LOGBACK-466
Merge pull request #163 from johngmyers/custom-archive-remover

Allow SizeAndTimeBasedFNATP subclasses to provide a custom ArchiveRemover
Update release notes for 1.1.0

Add note for SizeAndTimeBasedFNATP#createArchiveRemover
add support to log elapsedTime
Add 'D' pattern for elapsedTimeConverter
* Added support to the tomcat Server adaptor for correctly getting request start time. (Includes additional dependency on tomcat-coyote)
* Update layouts.html to document the addition of elapsedTime/D to the pattern support for IAccessEvent
* Modified AccessEvent.java to calculate the elapsedTime at construction of the event, instead of repeatedly in the getter.  This allows the value to be more easily seen in a debugger, and cleans up the code slightly.
* Fixed tabbing to be 2-spaces instead of 4
* changed direct access of timestamp field to use getTimstamp() instead inside of calculateElapsedTime.
* Undid some accidental roll-ups of imports, because my ide rules were set incorrectly.
* Added padding around NA, because my reformat took it away.
Merge pull request #142 from manuel-woelker/1.0.x

amendment for LOGBACK-644: suppress errors for nonexistent resource includes
Fixed issue "Failed to instantiate LoggerContext" because of " java.lang.SecurityException: AccessController.checkPermission is unsupported." (LOGBACK-760) using the solution provided in the comment by ori.
LOGBACK-350 Prevent SocketNode constructor blocking due to lack of data from client

The constructor creates an ObjectInputStream, and this blocks until the stream
header is received from the client.

If the client doesn't send a stream header, construction of the SocketNode will
hang, preventing SimpleSocketServer from accepting new clients.

This change moves the construction of the ObjectInputStream into
SocketNode.run. As SimpleSocketServer runs this method in a new thread, a rogue
client won't prevent subsequent ones being able to connect.
Mark SocketNode as closed if ObjectInputStream can't be created

This prevents a NullPointerException from being thrown, and allows the
socketNodeClosing method to be called for the SocketNode.
Validate ContextBase's status manager (LOGBACK-912)

We were null-checking the current status manager instead of the one
passed in.
Fix typo in Appenders documentation