Wrap history iterable to hide class implementation details.
Jelly was getting confused by the history underlying class being implemented
as an extension of Map

Document when EnvVars.get() function was added.

Set source/target level to 1.6 within the m2e profile.

Otherwise, eclipse gets unhappy with the @Override annotations.

inverse maven-plugin -> config-file-provider dependency

Added link to the pull request for "Changed defaults for the Mac installer to make iOS codesigning easier" in ChangeLog

Added link to the pull request of "Changed defaults for the Mac installer to make iOS codesigning easier"

[FIXED JENKINS-15733] ArrayIndexOutOfBoundsException from Launcher due to misinterpretation of ProcStarter.envs in f5cebdc8.
(Should this field be made a [LinkedHash]Map<String,String> or even EnvVars?
It is protected in a final class, so effectively package-private, thus not a b/w compat issue.)

Refactor handling of test mojos
Thanks

maven-failsafe-plugin deserves the same level of integration
as maven-surefire-plugin.

A failed IT should mark the build as unstable, not failed.