[JENKINS-18403] Commented-out bytecode level restriction for Maven process.
As in StreamTaskListener, the returned PrintWriter must be set to autoflush.
Otherwise the idiom t.printStackTrace(listener.error("…")) does not work.
[FIXED JENKINS-18403] Detect when an attempt is made to run Maven on JDK 5.
If so, retry with (6+) slave JVM, setting maven-{compiler,surefire}-plugin properties to point to original.
Merge branch 'master' of github.com:jenkinsci/jenkins
Groovy compiler doesn't seem to put the enclosing class information in the class file.
Fixing a test failure in RelativePathTest

It turns out that Groovy compiler we use to compile src/test/groovy was
not properly generating the 'enclosing class' information inside
*.class, which was causing the load failure of the descriptors marked
by @TestExtension in test code.

To fix this and forestall other possible GMaven related issues, I
decided to bump up the GMaven version. As it turns out, Codehaus GMaven
had ceased the development of the 1.x branch, so I initially tried 2.x
release line.

The 2.x release line got rid of the stub generation functionality, which
we badly need for annotation processing. It instead recommend using
Eclipse compiler to jointly compile Java and Groovy source code
together, but when I tried to compile our tests, it failed to properly
handle nested classes. The compiler quality appears quite premature.

I was then going back to GMaven 1.5, the last 1.x release. I took this
opportunity to rebase my local patches in org.kohsuke.gmaven to the
latest release, which in my mind gets justified now that the upstream
has ceased the development.

My local patch to GMaven is captured in GMAVEN-3 and GMAVEN-4
(see http://jira.codehaus.org/browse/GMAVEN-3 and
http://jira.codehaus.org/browse/GMAVEN-4).

GMAVEN-4 is claimed to be fixed, but when I tried to compile our source
tree I discovered that its handling of nested types breaks the generated
stub code.

In the end, I managed to patch gmaven and posted 1.5-jenkins-1.

The bottom line is, we can now use @TestExtension correctly with Groovy
tests. Also on the upside, we can get rid of org.kohsuke.gmaven and
avoid the current confusion situation of using two GMaven plugins.

I'll make a follow-up change to remove org.kohsuke.gmaven from elsewhere
in our POM.
This work around no longer necessary,

... as the newer Groovy compiler produces the proper enclosing class
infromation.
Replacing org.kohsuke.gmaven by org.codehaus.gmaven
Oops
[FIXED JENKINS-18485] Use correct node permissions in remote API

From now on user needs:
  Computer.CREATE to use 'create-node' CLI command
  Computer.DELETE to use 'delete-node' CLI command
  Computer.CONFIGURE to use 'update-node' CLI command and its REST alternative
  Computer.READ to use 'get-node' CLI command and its REST alternative