The earlier fix by @ssogabe broke the test. This fix corrects the
problem properly.

The reason this error happens with some plugins is that if there's an
input field whose name is "on", then even after prototype.js extends
an element object, "form.on" will refer to the input element, not the
prototype.js function to add an event handler.

(cherry picked from commit d8f74cf8)

Use DescribableList to handle the copy-on-write semantics correctly. The vector class just doesn't cut it, and we've been setting a new value to this field, which will violates all sorts of the concurrent programming practice.

This change has the nice side effect of removing {{class="vector"}} from the persisted XML. A test is added to make sure we can still read back such an XML.

Revisiting the fix. Avoid parsing the entire text by only looking at the tail portion.

This will hopefully reduce the file locking problems on Windows.

see
https://github.com/jenkinsci/jenkins/commit/2ffece9d737f4a77ed4059c777948299daf22771#commitcomment-3526425

Do not use anymore shaded version of wagon-http as it we can control commons-logging version

- if the user is anonymous, he'd go to HudsonAUthenticationEntryPoint, not here.
- even if there is some code path that comes here, there's no guarnatee that SecurityRealm in charge wants a login form.

This allows HudsonAuthenticationEntryPoint to access which permission was needed

... before making any modification.

The original version is acegi-security 1.0.7

Node monitoring should run in parallel to reduce the total round-trip
time in large instances.

Conflicts:
	test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java

Integrated the fix toward 1.521.