This reverts commit 836e52e6.

@Asynchronous does deliver method calls in order, but the receiver
might end up executing multiple calls in parallel, so it doesn't really
guarantee the in-order execution.

That makes @Asynchronous somewhat useless, so I need to fix that in
remoting. But until I do so, it's safer to back out this change.

Merge branch 'ArtifactManager-JENKINS-17236'

Fix recently introduced javadoc warning

Use an href for external URL in @see clause

[FIXED JENKINS-18721] Improvement of ListView render performance

Conflicts:
	core/src/main/java/hudson/FilePath.java
	core/src/main/java/hudson/tasks/ArtifactArchiver.java

[FIXED JENKINS-19034] restore missing buildnumber-ID symlink

[FIXED JENKINS-19418] Fix random HTTP 404 when viewing build details

Display the full display name in title for jobs and views

[JENKINS-18721] Imrovement of performance - now when ListView builds up it asks for all the jobs only once. This is important because RBAC plugin each time checks permissions for all these jobs which impacts performance

f:repeatableProperty documentation talks about including f:repeatableDeleteButton, but then fails to actually call d:invokeBody.
While you could put the delete button at the end of the nested config.jelly, this is ugly since it prevents reuse;
better to specify the delete button in the form using f:repeatableProperty.
f:repeatableHeteroProperty already inserted a delete button automatically, so its documentation was incorrect.

Observed in 1.509.2:
Parsing POMs
Failed to transfer Could not find artifact … in central (http://repo.maven.apache.org/maven2)
Archiving artifacts
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
java.lang.NullPointerException
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:138)
	at org.zeroturnaround.jenkins.LiveRebelDeployBuilder.getArtificatOrMetadata(LiveRebelDeployBuilder.java:194)
	at org.zeroturnaround.jenkins.LiveRebelDeployBuilder.uploadConfiguration(LiveRebelDeployBuilder.java:171)
	at org.zeroturnaround.jenkins.LiveRebelDeployBuilder.perform(LiveRebelDeployBuilder.java:108)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:812)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:828)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:779)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)
	at hudson.model.Run.execute(Run.java:1575)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:485)

In 1.516:
java.lang.NullPointerException
	at hudson.maven.ModuleName.equals(ModuleName.java:115)
	at hudson.maven.MavenModuleSet.reconfigure(MavenModuleSet.java:1108)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:907)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:631)

1. Use AtomicFileWriter on the hypothesis that an exception during save() caused truncation.
2. Improve logging from the cleanup thread since that may be related to the root cause.
3. Regardless of the cause, recover more gracefully by deleting any truncated file rather than throwing the error up.

Fixing copy-paste error