Added the toolLocations option to the CLI client
toolLocations get passed to the server
[maven-release-plugin] prepare release swarm-plugin-1.17
[maven-release-plugin] prepare for next development iteration
a quick test to see if I can parse the toollocations, see if they exist on the master and build their key
Merge remote-tracking branch 'upstream/master' into JENKINS-7543
Extracting SwarmClient to separate class;
Merge branch 'buzdin-master'
toollocations are registered on the master, and persist after a master restart
Merge remote-tracking branch 'upstream/master' into JENKINS-7543

Conflicts:
	client/src/main/java/hudson/plugins/swarm/Client.java
Added the possibility to define toollocations on the slave

toollocations are registered on the master, and persist after a master restart
Merge branch 'JENKINS-7543' of https://github.com/mrdfuse/swarm-plugin into JENKINS-7543
Added the possibility to define toollocations on the slave
Merge branch 'JENKINS-7543' of https://github.com/mrdfuse/swarm-plugin into JENKINS-7543

Conflicts:
	plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java
Merge pull request #17 from mrdfuse/JENKINS-7543

Set tool locations from Swarm plugin CLI

Swarm plugin CLI agent cannot specify tools (JDK, Maven, etc) locations on the slave host.
Locations can differ among slaves - especially if slave OSes are different.
Automatic tool installation does not suit for many cases - shared slaves, custom tool variations.

Closes https://issues.jenkins-ci.org/browse/JENKINS-7543
[maven-release-plugin] prepare release swarm-plugin-1.18
[maven-release-plugin] prepare for next development iteration
[JENKINS-24995] fixed exception when not passing any toollocations
Merge branch 'mrdfuse-JENKINS-24995'
[maven-release-plugin] prepare release swarm-plugin-1.19