Prevent ClassCastException when encountering ItemGroup of
non-TopLevelItem.

This is the case for instance when encountering a MavenModuleSet which
is ItemGroup<MavenModule>
add global maven config to define default settings providers
[FIXED JENKINS-17030] Enable word breaking for job names
Add extension point to rewrite JUnit test names

This adds an extension point, TestNameTransformer, which is called to transform JUnit test case names.
This is useful for JVM languages like scala which are more flexible than java with identifier naming.
Scala, for example, allows you to write test names between back ticks, and then encodes the name using valid java identifiers.
This extension point would allow a plugin to transform those names back in to readable names when they are displayed on the test result page.
If an optional component cannot be loaded, print a polite one-line message, not a big scary stack trace.
(To reproduce: BuildNowTextPropertyTest from cloudbees-template warns about FolderProxyGroupContainer.)
Merge pull request #769 from dnadolny/master

[FIXED JENKINS-17478] Add extension point to rewrite JUnit test names
try using defaulting of dropdownDescriptorSelector
[FIXED JENKINS-17723] add test cases to verify defaulting global settings providers
[FIXED JENKINS-17858] allow <f:dropdownDescriptorSelector> to be defaulting to a specifig instance
Merge pull request #772 from imod/default-maven-settings

FIXES JENKINS-17723 - Default maven settings
Good change !
Update changelog.html

changelog entry for JENKINS-17723
Merge pull request #771 from imod/dropdownDescriptorSelector-defaulting-to-instance

[FIXED JENKINS-17858] allow <f:dropdownDescriptorSelector> to be defaulting to an instance
Update changelog.html

changelog entry for JENKINS-17858
Auto-restart the service if it fails.
looks like this moved to the plugin section
Added windows sevice auto-restart support.
Frequent test failure on PR builder.
Invalid request submission: {json=[Ljava.lang.String;@2c46358e, .crumb=[Ljava.lang.String;@35661457}
Diagnostics added in 21bf5c4.
Failing I think because message.groovy uses f.submit rather than a plain <input type="submit">,
so JSON gets created and then StaplerRequest.getParameter cannot find it.
But if this is the problem then why would it ever work?
Perhaps a timing issue: JavaScript is used to massage the form just prior to submission,
and maybe this only happens sometimes?
Cannot reproduce test failure locally.
JUnit 4.
Skipping slave test on PR builder since it often fails.
JUnit 4.