items, which upgrades the versions used for maven-hpi-plugin,
maven-stapler-plugin and maven-localizer-plugin

upgrade to maven 3.0.3 (will prevent issue when pom parsing phase : http://jira.codehaus.org/browse/MNG-4963)

take care about using settings from the remote node

If you had two clouds and only the second one could provision a label, it'd never get that far - check to see if a cloud can provision a label before trying to do so.

I wasn't initially planning to do this, but it turns out more people needed this feature than I thought.

I left the text as is, but defined a mechanism to override this in the plugin, in a possibly context sensitive way. For example, a plugin can replace this text on a job-by-job basis, or by looking at some property/builder/etc.

While the original report is in https://cloudbees.zendesk.com/tickets/427, this fix also takes care of JENKINS-4220.

[FIXED JENKINS-8917] Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins".

the master.

Set M2_Home for maven builds and add maven to the path so if the build
needs to run maven from maven (or maven from ant from maven) it can.