Rewrite the docs to fit the current best practices for Puppetlabs
modules.
revert concat $warn/$warn_message param split + add deprecation warnings

Partially reverting the $warn/$warn_message param split from eaf8407 as this
change was unnecessarily API breaking.  Instead, we are adding string/bool type
validating to the $warn parameter and deprecation warnings for the usage of
stringified boolean values (eg, 'true', 'on', etc.). In a future major release,
the logic can be simplified to treating all string values as a warning message.
Merge pull request #124 from jhoblitt/revert_warn_message

revert concat $warn/$warn_message param split + add deprecation warnings
add README section on API deprecations since version 1.0.0
Merge pull request #1 from jhoblitt/docs-change

add README section on API deprecations since version 1.0.0
Merge pull request #114 from apenney/docs-change

Rewrite the docs to fit the current best practices for Puppetlabs
work around RubyGems 2.2.0 breaking ruby 1.8.7
Merge pull request #126 from jhoblitt/rubygems_220_travis_workaround

work around RubyGems 2.2.0 breaking ruby 1.8.7
1.1.0 release.
Add information on deprecations.
Merge pull request #125 from apenney/200-release

1.1.0 release.
remove workaround for Rubygems 2.2.0 bug

https://github.com/rubygems/rubygems/pull/763 is merged and released in
Rubygems 2.2.1. A forced downgrade is no longer required.
Merge pull request #127 from 3flex/remove-rubygems-2.2.0-workaround

remove workaround for Rubygems 2.2.0 bug
Correct the version we're releasing.
Add workaround back in, problems still happening.
Merge pull request #128 from apenney/110-rc1-release

Correct the version we're releasing.
Convert specs to beaker and increase coverage
Merge pull request #131 from hunner/update_specs

Convert specs to beaker and increase coverage
Fix ensure => absent with path => set.

The current code doesn't correctly account for an absent with a
path set, incorrectly trying to remove $name instead.  Fixing this
raised the issue that fragments left with no ensure will fail when
absent is set as the fragdir is deleted.

As a workaround for this we check the `ensure` parameter from the
concat{} resource with getparam() and then pass that to the fragment
if no specific ensure was passed in.  This effectively ensures
fragments inherit their parents ensure status.
Fix the tests by switching to stdlib 4.x instead of 3.x.

getparam() unfortunately only arrived in 4.x, so switch.