Updated README file with details about NoThreadScheduler
This test is failing randomly on the slow ec2 instances, so increasing margin for error
Adding more features to the README (though these are better formatted and describe in the wiki)
This test should also be more tollerant of slow ec2 systems
Another time condition that is too tight (not sure why ec2 is so much slower now)
Updated the javadocs for TaskExecutorDistributor and TaskSchedulerDistributor
This should better clarify some questions we got from reddit.
Some minor interface improvements
I was trying to do some performance improvements (but could not quite get them working right).  These were some changes I found along the way that I wanted to maintain:
* BlockingQueueConsumer handles inheritance better by using extends and super for generics
* PriorityScheduledExecutor only needs a runnable to provide into the workers now
* DynamicDelayQueue's ConsumerIterator is a bit more efficent, and now checks for ConcurrentModificationExceptions which corrupted the traversal
Minor change to reset thread's interrupted status here
Added a few more unit tests, focusing around error conditions
No new bugs found, or functional changes, just more unit tests and more code coverage.
Expanded utilities for working with listeners and callbacks in event driven designs
I added "CallbackHelper" to go along with "ListenerHelper"...ListenerHelper is still the implementation to use with runnable listeners, but CallbackHelper can help reduce code for interfaces where callbacks have multiple functions, or arguments that need to be provided.
Because of this I put both into a new package (org.threadly.concurrent.event).  The old ListenerHelper is now marked as @Deprecated, and will be removed in 3.0.0
Issue #95 covers eventually removing this for the 3.0.0 release

Eventually if this package gets too big, we may seperate this into another project under the org.threadly groupings.  Right now it is small enough that I don't think this is warrented.
Merge pull request #96 from threadly/unstable_staging

Expanded utilities for working with listeners and callbacks in event driven designs.
Fix for generics, we need to allow super classes here to be more flexible
Renamed ListenerHelper into RunnableListenerHelper and renamed CallbackHelper into ListenerHelper
This makes the naming more consistent, as I don't think I was really defining the distinction between a listener and a callback well enough.
Having runnable in the name for the now 'RunnableListenerHelper' also makes it clearer as to what it's design is for.

This also makes the interfaces more similar between them, possibly making it easier to extend these (or put them under a common interface) later
Added more details to this javadoc
Changes to make it easier to extend the ListenerHelper, and adds AsyncCallListenerHelper
The AsyncCallListenerHelper implementation makes it so that the .call() functions will never block (by just running within the executor provided at construction time).
This also has javadoc improvements for existing functions, making it clear what is necessary when providing an executor to prevent concurrent execution of listeners.  I got a bit worried people might accidently shoot themselves in the foot the more I considered it.
Added AsyncCallRunnableListenerHelper
This is very similar to AsyncCallListenerHelper, except again designed around listeners which use the runnable interface.
Added "DefaultExecutorListenerHelper" and "DefaultExecutorRunnableListenerHelper"
These should cover the other point where we don't want the .call()/.callListeners() to block.  Instead of having these invokations happen on an executor, we just ensure that ALL listeners have an executor associated to them.
This is better for when there is few listeners, but those listeners have a high complexity/run time.  Where the AsyncCallListenerHelper/AsyncCallRunnableListenerHelper are better when there is a possibly high qty of listeners, but the listeners execute rather quickly.  The normal ListenerHelper/RunnableListenerHelper are best when there is a low qty of listeners, and they execute quickly, or when blocking on the calling of the listeners is not an issue.
Update README with details about expanded ListenerHelper functionality
Update README.md
This resolves #87 - Renaming PriorityScheduledExecutor into PriorityScheduler
@joshuawarner32 convinced me to go ahead with the rename (which I was leaning to slightly ahead of time, and obviously attempted once before 2.0.0).
This rename should be pretty complete, but it is completely backwards compatible.  This renames PriorityScheduledExecutor into PriorityScheduler...as well as renames PriorityScheduledExecutorServiceWrapper into PrioritySchedulerServiceWrapper.
This should be a completely backwards compatible change, the old classes still remain, and are just marked as deprecated.  They will be removed in the 3.0.0 release.