Use proper dates in QueueItems, fix broken logic.

Use Java8 date types for parser queue items. Fix the time check in
QueueHandler to check if the item has been queued for longer than
10 seconds, rather than if the item was created within 10 seconds
of the epoch.

Update dagger.

Update dependencies.

Add numeric stuff to IRCDataInEvent

Minor inconsequential parser tidying.

Send QUIT on disconnect. (Close #7)

Add IRCDataInEvent that presents a ReadLine object rather than just the line of data.

No point using 2 separate queue's for pendingKeys

This gives us access to MessageTags (#19) and pre-tokenised lines in DataIn rather than everything neededing to tokenise themselves.

There are probably a few other events we want to expose messagetags on that we still don't.

Make ProcessJoin handle the pendingJoins queue.

Issue #108

Try to keep track of channel keys (Close Issue #108)

 - Parses outgoing JOINs to try and guess keys before we get the MODE reply.
   - Parsing algorithm based on Quakenet/Hybrid handling of keys.
     - Keys are swallowed from the key-list for EVERY channel that is
       to join, even if it is not needed, so you would need to use
       "JOIN #Foo,#Bar,#Baz Foo,,Baz" to join keyed channels #Foo and #Baz.
 - Key changes by mode +k and -k will be tracked.
 - Ignores attempts to set the key as "*" if we know a "better" key.
   - Side effect: If the key is actually set to "*" we can only learn it if that
     is what we join with, or it gets changed to that from no-key.

Some additional WHOIS bits that were missed.

Tidy up a few asserts.

Migrate parser events to use new date APIs.

Java 8 introduces a sane API for dates; to store datettimes
we should now be using LocalDateTime.

Actually set the event bus error handler...

Update to MBassador 1.2.4.

This release contains some performance improvements compared
to the version we were using.

Error handlers are now passed in at construction time, so
there was a small bit of refactoring required.

Set ADDRESS and REAL_NAME property after whois.

Having two separate events means the ordering isn't guaranteed.
Handle everything for 311 numerics in one handler.

Don't allow resetting state whilst socketClose events are still occuring

Always provide a 'kicker' client.

When we moved to events, we stopped passing null in place of clients.
Instead, fake clients should be used. Apparently ProcessKick wasn't
properly updated.

Fixes issue #100

Modes should default to "" not null

Bump gradle version.