[JENKINS-21014] include verify in upstream candidate calculation
[JENKINS-21014] include verify in upstream candidate calculation
- changed test to make sure that dependencies for test projects are available in repository
upgrade maven release plugin version
[maven-release-plugin] prepare release maven-plugin-2.3
[maven-release-plugin] prepare for next development iteration
unused message (orphaned since 5848d3f08584eccd11336e293d3ace305c9e1bd0)
unused message (orphaned since 76740511a1ec268652ee3f5b1e25189fd48b55e5)
Merge pull request #19 from christiangalsterer/master

[JENKINS-21014] include verify in upstream candidate calculation
updated help
updated German localization
consistently use "maven" for the maven project type

For the maven project type several names were in use: "maven", "maven2", 
"maven2/3", "maven 2/3".

The 2 and 2/3 variants seem to stem from times when the maven job type
only supported maven 2 while maven 1 still was widely used. 
This is no longer relevant, see
http://maven.apache.org/maven-1.x-eol.html.

I adapted the use of the prominent job pronoun, "maven", which also
reads much better than the 2/3 variants
[JENKINS-11814] [JENKINS-20487] Cleaning up dead code now that MavenArtifactArchiver does not call recordFingerprints.
[FIXED JENKINS-11333] Allow users to disable automatic fingerprinting, but add in explicit fingerprinting if desired.
SOAPUI Extension | Change of groupIds

- According to http://www.soapui.org/Test-Automation/maven-2x.html the groupId has been changed from eviware to com.smartbear.soapui and the artifactId from maven-soapui-plugin and maven-soapui-pro-plugin to soapui-maven-plugin and soapui-pro-maven-plugin

- It would also be great if the maven-soapui-extension-plugin could be supproted https://github.com/redfish4ktc/maven-soapui-extension-plugin/wiki
SOAPUI Extension | Change of groupIds

- According to http://www.soapui.org/Test-Automation/maven-2x.html the groupId has been changed from eviware to com.smartbear.soapui and the artifactId from maven-soapui-plugin and maven-soapui-pro-plugin to soapui-maven-plugin and soapui-pro-maven-plugin

- It would also be great if the maven-soapui-extension-plugin could be supproted https://github.com/redfish4ktc/maven-soapui-extension-plugin/wiki
Merge pull request #23 from rompic/patch-1

SOAPUI Extension | Change of groupIds
Merge pull request #24 from rompic/patch-2

SOAPUI Extension | Change of groupIds
Module config.xml files were confusingly starting with <maven2-module-set> (as distinct from <maven2-moduleset> for the top-level config.xml).
This was the old mistaken value which we need to be able to *read* but should never *write*.
Every time you call XStream.alias, you are setting the new default element name for saving,
yet the code was mistakenly setting the compatibility alias after the desired alias.
If MavenReporter.postExecute threw IOException, something might be seriously wrong, so mark the build as failed.
For example, this has been observed to happen during test result archiving due to an as-yet-undiagnosed NCDFE,
where there were test failures yet this error allowed the build to be considered successful:
Tests run: 43, Failures: 0, Errors: 4, Skipped: 0

[ERROR] There are test failures.

Please refer to …/target/surefire-reports for the individual test results.
[JENKINS] Recording test results
java.io.IOException: Remote call on channel failed
	at hudson.remoting.Channel.call(Channel.java:748)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)
	at com.sun.proxy.$Proxy7.execute(Unknown Source)
	at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:201)
	at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:160)
	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628)
	at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
	at …
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117)
	at …
Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.tasks.test.TestObject
	at sun.misc.Unsafe.ensureClassInitialized(Native Method)
	at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(Unknown Source)
	at sun.reflect.ReflectionFactory.newFieldAccessor(Unknown Source)
	at java.lang.reflect.Field.acquireFieldAccessor(Unknown Source)
	at java.lang.reflect.Field.getFieldAccessor(Unknown Source)
	at java.lang.reflect.Field.getLong(Unknown Source)
	at java.io.ObjectStreamClass.getDeclaredSUID(Unknown Source)
	at …
	at java.io.ObjectInputStream.readObject(Unknown Source)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at …
[INFO] 
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ … ---
…
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
…
channel stopped
Finished: SUCCESS
[maven-release-plugin] prepare release maven-plugin-2.4