Add LICENSE file. Update Modulefile to use ASL instead of APL to refer to the Apache License.
Merge pull request #12 from haus/add_license_file

Add LICENSE file. Update Modulefile to use ASL instead of APL to refer t...
Update Modulefile version to 0.0.4
Work around keytool err on empty (zero-byte) file

Previously, puppet would give the following keytool error when :target
is an empty file.

    err: /Stage[main]/Pe_mcollective::Ca/Java_ks[puppetca:truststore]/ensure: change from absent to latest failed: Execution of '/usr/bin/keytool -importcert -noprompt -alias puppetca -file /etc/puppetlabs/puppet/ssl/certs/ca.pem -keystore /etc/puppetlabs/activemq/broker.ts -trustcacerts' returned 1: keytool error: java.lang.Exception: Keystore file exists, but is empty: /etc/puppetlabs/activemq/broker.ts

This commit resolves the problem by writing the keystore to a temporary
file, if the target is empty, and then copying the newly generated
keystore into the original target (thus bypassing keytool's reluctance
to interact with empty files).
Merge pull request #13 from reidmv/fix/empty_target_bug

Fix/empty target bug
Update Modulefile for 0.0.5
Add simple workaround for empty file issue

commit 82fdb1b6 did not quite fix the problem.

We tried to do more complicated things but in the timeframe we had, ran
into some hard-to-trace issues on SLES of all things, discovered that
the codepath forked and java keytool commands which would blow up on
empty target keystores existed in two places, and tested stuff lots.

This fix is simple, kinda stupid, and should just work. Because there
are two codepaths that (previously) called keytool commands which could
error out on an empty target file, the new empty file hack is installed
in its own dedicated method.

We also revert the tmpfile method used previously for the simpler more
straight-forward algorithm:

  1. If a target file exists but is zero-length, stat it, then delete
     it.

  2. Run the java keytool command.

  3. If during step 1 a file was statted, apply the owner/group/mode to
     the (presumably) new file.

Conflicts:
	lib/puppet/provider/java_ks/keytool.rb
Fix Suse bug
Add defined? fix for Suse

The funky double-take check is because on Suse defined? doesn't seem to
behave quite the same as on Debian, RedHat. Wow. Combined with the issue
where IBM Java keytool won't take a password on stdin that took a long
time to track down.

Contributors:
Branan Purvine-Riley
Reid Vandewiele
Merge pull request #14 from reidmv/fix/empty_target_bug_rm

Fix/empty target bug rm
Update Modulefile for 0.0.6
Remove deprecation notice from Puppet 3.x.

  Before this commit the 3.x series of Puppet would throw a deprecation
  notice for the use of Puppet::Util.execute.  In order to remove this
  warning we will detect for the existence of the new replacement
  method, Puppet::Util::Execution.execute and if it exists we use it.
Fixes all failing unit tests.

  Previously several of the unit tests that were defined for this
  module were broken.  This was discovered while fixing Puppet 3.x
  deprecation warnings.  This patch fixes all tests and adjusts provider
  code where is was causing legitimate failues.
Updated content to conform to README best practices template

Before alterations, this content was the module author- determined
description of and instructions for use of the module.

As part of a joint Forge/Docs team effort to standardize formatting and
encourage quality module documentation, a best practices README
template was created via internal and external user testing. That
template was then applied to this module.

I pulled in content from the original README on GitHub. Standard
headings were added (Overview, Module Description, Setup, Usage,
Implementation, etc.) to organize content, existent content was moved
under its appropriate heading and edited for tone/flow/clarity, and
basic formatting was done to adhere to template standards.
Merge pull request #16 from laurenrother/master

Updated content to conform to README best practices template
Merge remote-tracking branch 'ody/puppet_3_deprecation'
Refine general keytool provider execution method
Use "-v" in keystore -list. Java 7 will output SHA1 fingerprints by default, prior it was MD5. Otherwise certificate is re-imported on every Puppet run.
Explicitly set random file for OpenSSL. Fails otherwise. Grrrr.

Conflicts:

	lib/puppet/provider/java_ks/keytool.rb

Merged by: Reid Vandewiele <reid@puppetlabs.com>

Note: during the merge I took the liberty of modifying the means by which
RANDFILE was set for code execution, so as to avoid leaving the env
variable set in the Puppet process proper
Merge branch 'randfile_openssl'