Adding a new notification strategy "new failure and fixed".

It's similar to "failure and fixed" but does not notify of repeat failures.  This is useful because when a build fails and is set to rebuild automatically, you do not want to spam IRC with repeat failures.  The new strategy is also similar to "change", but change includes aborted builds and success after an aborted build, which we don't care about.  In particular, restarting jenkins while builds are taking place aborts the current builds, then rebuilds them on startup.  Even if the build succeeds, it will notify IRC that it went from Aborted to Success.
Merge pull request #8 from jlabanca/jlabanca/new-failure-strategy

Adding a new notification strategy "new failure and fixed"
Less expensive way to fetch the top-level jobs
Jenkins!
[FIXED JENKINS-17565] allow to address jobs by displayName in bot commands
replace deprecated Assert
added a Readme
Fixed tests
Yippie = Youth Independence Party Member
Handle parameters based on the ParametersDefinitionProperty from the
project, so default value are handled as well.
Merge pull request #10 from williambernardet/master

[FIXED JENKINS-19140] Fix the handling of (default) parameters for project triggering.
minor clean up
Refactor parameter parsing into a separate method
Arrays.copyOfRange is Java 6+
Refactored the 2 existing parameters test cases into 2 separate methods
Support all 'simple' parameter values
These are not very useful verifies
roll forward after broken release
[maven-release-plugin] prepare release instant-messaging-1.27
[maven-release-plugin] prepare for next development iteration