Turns out there was a security advisory posted on Ant 1.8.3
(http://ant.apache.org/security.html) though the affected code is not
used in Jenkins.

Reference: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2098

Integrated the change

(cherry picked from commit 5e7b844b)

Conflicts:
	changelog.html

(cherry picked from commit 9b53643c)

Conflicts:
	pom.xml

See https://github.com/jenkinsci/maven-plugin

(cherry picked from commit f98070d3)

Conflicts:
	maven-plugin/pom.xml
	maven-plugin/src/main/java/hudson/maven/AbstractMavenProcessFactory.java
	maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
	maven-plugin/src/main/java/hudson/maven/MavenProcessFactory.java
	maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly
	plugins/pom.xml
	pom.xml

Integrated the fix in remoting to Jenkins 1.580.

Seems to work in 8.0 at least for some functional tests.
Developers can always disable it privately if they run into issues.
(cherry picked from commit 7b420175)

Conflicts:
	pom.xml

Integrated a bridge-method-injector that rebuilds the constant pool from
scratch.

Integrated remoting.jar that fixes the problem