added some debug logging
added some more explicit logging
changed the configuration of XmlPullParserFactory because it was causing problems when botto was imported in another project.
Added a new Injectable @Contect type, ConnectionStatus, to let bots know their connection status

Bot implementors can now add a field @Context ConnectionStatus that will be updated
with the bot connection status as it changes. Note, at this point not thought
has been given to multi-threading implications.
Wired the ConnectionStatus object for single-bots.
Modified ConnectionStatus from enum to interface (ConnectionInfo)

ConnectionInfo allow for the implementation to be thread safe (see BotConnectionInfo)
and allows for future extensions of connection info
Setting initial connection status for subdomain bots
Fixed dropwizard example project
Updating docs and pom to be in line with snapshot 0.7.0
Added a wrapper for elements in QueueExecutor

Ground work for #4 - the wrapper allows to transport process results and set futures
QueueExecutor.enqueue now returns a ListenableFuture

Ground Work for #4
- also improved shutdown code following guidelines in http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ExecutorService.html
Spinned off QueueExecutor to project java-reusables-threading
Small refactoring and cleanups

- aligned some class to java-reusables 1.1
- componentBotExecutor tasks now can return a Future<Packet>
- BotSessionPacketSender.send now returns a ListenableFuture, to enable full tracing of packet flows
- improved log gin and shutdown when a component connection fails
Improved logging on initial BotSession login failure
Completed wiring of the new DispatcherService with AbstractService2
Removed per-session single threaded sender

With the new implementation, outgoing messages are already de-queued asynchronously from an outgoing queue, so the embedded queue worker is not required anymore.
Initial work on abstracting the connection technology from dispatcher and service

Introduce a new set of abstractions (Connector, BotConnection) and specific implementations for Whack and Smack.
This simplifies the design of Dispatcher, as packets are now always sent and received but a BotConnection, regardless
of the underlying connection technology.
Concrete Connectors now need to implement Connector<ConnectorConfiguration>
Small engine api changes
Initial work on an Engine launcher