Using mojo extra-enforcer-rules enforceBytecodeVersion.

This rule enforces a bytecode version in dependencies.
This would prevent cases like JENKINS-8914 where someone had
introduced a dependency compiled with JDK1.6 at a time where
Jenkins was still on 1.5.

With 1.7 already here and 1.8 coming, this should help no to do that
again.
Using a property to share target jdk version with enforcer rule.
[JENKINS-18282] Introduce get-node CLI command
[JENKINS-18282] Introduce update-node CLI command
[JENKINS-18282] Introduce create-node CLI command
Introduce CLICommandInvoker for testing purposes
[FIXED JENKINS-18282] Optionally override name from XML in create-node CLI command
[FIXED JENKINS-10184] wrong timestamps in build timeline - added
Daylight Saving Time
JENKINS-18429 fixes
Better plugin description in root jelly
Add tests for MyViewTest class
Add minPermGen and minHeapSize settings for defaults(1) which will be used preallocate Java's HeapSize and PermSize.
Set defaults for Java heap and perms on both i386 and x64_64 architectures. The x64_64 settings work for me. Recommend that they be reviewed by a Java/OSX dev.
[FIXES JENKINS-15976] After de-serializing changed job settings after "Save", the maven settings done by config-file-provider-plugin were overwritten blindly (presumably with fallback values). These fallback values should be set correctly in the constructor of the "Maven" class and do not need to be set explicitly after deserialization.
Add convenient method for checking if object is MatrixProject

This is useful for jelly pages where instanceof operator doesn't work.
Loading the last 3 successful builds may be very expensive in certain rare, but possible situations (all newer builds failed, only some very old builds were successful).
Go only up to 6 build into the past for calculating the estimated duration.
Also take failed builds into account, if we don't find any successful ones.
Merge branch 'master' into node-cli
Delete “No” button when renaming; does not work reliably anyway.
Going back in browser history can reset configuration form to the *previous* state,
not what was just saved! (In the case of lazily inserted form elements.)
Thus clicking Save from that page would actually revert your recent changes.
For now, just omitting the button; could make it go back to index or configuration pages,
but there are already links for this.
Add unittests for Util.loadProperties
added translation for SecurityIsOffMonitor (de)