Based on the work of Michael Elkin [1].

[1] https://issues.jenkins-ci.org/secure/attachment/20588/0001-tag-1.414-for-parameters-in-multiconfig-filters.patch

changelog entry for JENKINS-17858

changelog entry for JENKINS-17723

[FIXED JENKINS-17681] Do not try to call resolveSymlink on a nonexistent link as you will just get an IOException, breaking peephole permalinks in some Windows environments.

[FIXED JENKINS-17775] Find (model) parent POMs properly during fingerprint recording at end of build.

[JENKINS-17775] If MavenProject.getParent throws ISE during fingerprinting, report it but at least proceed.
Proper fix is to ensure that the model resolution uses the same environment as the actual build,
or is otherwise more lenient about finding the parent (e.g. enables plugin resolution).

A recent Stapler update caused the Jelly facet to ignore *.xml.
So need to use raw j:include (as plugins were doing), not st:include (as core did).

Most notable, cvs 1.6 → 2.8, to get the critical fix of removing the mail address resolver.

Object that implements ModelObjectWithChildren can expose its children in the breadcrumb.

Added logging more liberally, and fixed the problem.
The root cause was that when the mouse enters a hot spot, I wasn't cancelling the previous delayed hide timer.

This fix eliminates the need for the hack in the hide method where I was testing if the mouse was still over the hotspot.

Using l:confirmationLink instead of AbstractItem/delete.jelly and AbstractProject/wipeOutWorkspace.jelly.

Expanded MockFolder to be a ViewGroup so that it is possible to test views inside folders,
and generally fixed it to service Stapler hierarchies properly so that WebClient-based tests can work.

[FIXED JENKINS-15340] Ask for confirmation before reloading config from disk, as it may be expensive.
First of all, /reload should require POST (also prevents XSS DoS attacks).
Adding <l:confirmationLink> to encapsulate a link that requires confirmation upon clicking.
Allowing a ManagementLink to request confirmation (also implying POST); could be used also for e.g. /quietDown.
Enhancing <l:task> to support confirmation as well, and honoring this in context menu items.