22860 - --force should set --no-splay

--froce is documented as "Will force a run immediately else subject
to default splay time" but prior to this patch this wasn't the
actual behaviour.
Merge pull request #8 from richardc/bug/master/22860

22860 - --force should set --no-splay
release version 1.6.1
maint - run the spec tests only once

joining on -I makes the first element not have a -I in front of it.  This just
happens to be `pwd`/spec, so rspec runs each spec file twice, once for the
implcit argument from it's spec/**/*_spec.rb expansion, and then again because
it recursed over `pwd`/spec.
22370 - Add a parse_log parameter to the last_run_summary action

This commit adds a parse_log parameter to the last_run_summary
action.  When true the report will will be parsed and summarized in a logs
subkey.
add testing for parse_log option

The previous test used a test value for logs that was the same as it not
calling the method.  This patch changes this and also adds explicit testing for
the parse_log parameter.
Merge pull request #9 from richardc/parse_logs

22370 - support parsing the report as part of last_run_summary
(MCO-28) Change noop to no-op for front-end text

Prompts and descriptions from puppet.ddl are used on the front-end of
Puppet Enterprise's Live Management to describe actions to users. For
ticket PE-2150, we need to change all user-facing instances of "noop" to
"no-op."
(MCO-28) Change noop to no-op for front-end text

Bump version and update changelog
MCO-31 Change method of running puppet to double-fork foreground run

Specifying `--daemonize --onetime` causes quite an amount of confusion
by running puppet as a daemon, but for the semantics of a one-off backgrounded
run.  See PUP-1320 for more discussion of this issue.

This patch makes use of the usually uncalled
MCollective::Util:PuppetAgentMgr#run_in_foreground method, and then
when running a command from MCollective::Agent::Puppet#run we
double-fork and exec to dissasociate the process from the mcollective
daemon, and run optimistically in isolation.  This is the same model
as used on Windows, brought to Unix flavours.
Merge pull request #11 from richardc/mco-31

MCO-31 Change method of running puppet to double-fork foreground run
maint - the plugin install guide moved

Point at docs.puppetlabs.com's newer version rather than the old redmine wiki.
maint - the official gem is called mcollective-client

When I added the initial travis testing in 779969 I feel into the not uncommon
trap of thinking the official gem would be called 'mcollective' and not
'mcollective-client'.

Here we tweak the Gemfile to test against that instead
maint - add mcollective 2.4.x to travis matrix
Merge pull request #14 from richardc/travis_2_4

Add MCollective 2.4.x to the testing matrix
With mcollective 2.4.1, I am unable to pass --no-noop and --no-spray.
Inspecting the configuration hash, it appears that when specifying a --no- option on the command line,
the configuration[:attribute] is set to false.

Checking if the hash includes the no_noop/no_spray options so that we do not break compatibility with 2.2.x installs.
Process should be referenced using the fully qualified class (::Process).

When the process agent is also deployed, Process gets resolved in MCollective::Agent::Process, thus breaking things.
Merge pull request #13 from m4ce/master

Fixes command-line parsing under mcollective 2.4.x and 2.3.x.
Fixes interaction with mcollective-process-agent by qualifying references to ::Process
maint - make the spec tests a little more robust

Some tests were reliant on other tests loading/defining namespaces for them,
which meant you couldn't run the spec tests in isolation, only in the whole.

This commit adds missing require lines to ensure the aspects of the module
under test are loaded as expected.

Flushed out with this snippet:

    for spec in $(find spec -name \*_spec.rb); do echo $spec; bundle exec rspec $spec; done
Merge pull request #15 from richardc/make_specs_more_robust

maint - make the spec tests a little more robust