Don't grab the Jenkins user credentials if none are selected
Use the new CredentialStore interface and ensure upgrades are atomic
make development easier

- Given that ssh-slaves is bundled it can be difficult to test with hpi:run
When there are multiple key files for the same user name, upgrade can make it hard to differentiate
Use a more forgiving of minor formatting differences comparison of PEM keys
Update to ssh-credentials 1.5.1 to ensure any borked keys from upgrade are fixed
[maven-release-plugin] prepare release ssh-slaves-1.3
[maven-release-plugin] prepare for next development iteration
Fixes link in help text for adding credentials

The hardcoded '../../credentials' pointed to a wrong location if you have
Jenkins running e.g. 'on www.servername.com/ci'. The 'rootURL' handles
this.

Change-Id: I8b6d529aca31b5b7a28d02fde0c4b86b9dbb7b3c
Signed-off-by: Aske Olsson <aske.olsson@switch-gears.dk>
Merge pull request #14 from dvaske/master

Fixes link in help text for adding credentials
[FIXED JENKINS-19758] Trilead SSH was closing the logger stream on Jenkins 1.521+
[maven-release-plugin] prepare release ssh-slaves-1.4
[maven-release-plugin] prepare for next development iteration
fixed link in help file for existing localizations

see https://github.com/jenkinsci/ssh-slaves-plugin/pull/14
Use new credentials <c:select/> tag so that whe credentials plugin adds a "Add credentials" UI we can take advantage of the addition
Use new credentials <c:select/> tag so that whe credentials plugin adds a "Add credentials" UI we can take advantage of the addition
Should be pulling credentials from the request's ItemGroup context rather than assuming it's Jenkins as that allows a Cloud to have its own credential store
[maven-release-plugin] prepare release ssh-slaves-1.5
[maven-release-plugin] prepare for next development iteration
Upgrade default jdk install from jdk-6u16 to jdk-6u45 because jdk6u16 is outdated.
Added static final DEFAULT_JDK variable containing default jdk install id.