[JENKINS-18485] Enable Computer.EXTENDED_READ permission using "hudson.security.ExtendedReadPermission".

    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.EXTENDED_READ to use 'get-node' CLI command and its REST alternative

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

... as the newer Groovy compiler produces the proper enclosing class
infromation.

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.

If so, retry with (6+) slave JVM, setting maven-{compiler,surefire}-plugin properties to point to original.

Otherwise the idiom t.printStackTrace(listener.error("…")) does not work.

"Manage Credentials" is defined in credentials-plugin. I will create a
pull request for that as well.

Merge branch 'prevent-too-recent-bytecode-in-deps' of github.com:Batmat/jenkins into Batmat-prevent-too-recent-bytecode-in-deps

Integrated the fix into Jenkins

[FIXED JENKINS-18641] <st:bind> tag adds <script> tag. This extra tag caused syntax error if JQuery plugin enabled.

This was the change suggested by Jesse.

Add logging for colliding resources

[FIXED JENKINS-18282] - Manipulate nodes via CLI

[FIXED JENKINS-17942] Break long values in property tables

[FIXED JENKINS-10184] wrong timestamps in build timeline.

I'm going to just merge this in for now and welcome anyone who finds the proper way to do this.

Add more control of Java heap and perm sizing on OSX and set defaults. 

Add tests for MyViewsProperty class

Tests for User class.

Add tests for MyViewTest class

[FIXED JENKINS-18196] Change to the estimated duratrion calculation to prevent performance issues with lazy build loading

Poll on the last existing workspace instead of the last workspace,