[JENKINS-14585] MavenTestDataPublisher didn't do anything
no longer only about UTF-8
Don't do memory mapped file unless it's helpful.

This will hopefully reduce the file locking problems on Windows.
[FIXED JENKINS-15382]

Revisiting the fix. Avoid parsing the entire text by only looking at the tail portion.
Forgot to close the file
not sure which code is triggering animal sniffer violation
removed Java 1.6 dependency
added l10n(ja)
[maven-release-plugin] prepare release jenkins-1.521
[maven-release-plugin] prepare for next development iteration
updated changelog for release
Fixed an overzealous form validation
Pushing the dependency computation down to another thread.
[FIXED JENKINS-18589]

Use DescribableList to handle the copy-on-write semantics correctly. The vector class just doesn't cut it, and we've been setting a new value to this field, which will violates all sorts of the concurrent programming practice.

This change has the nice side effect of removing {{class="vector"}} from the persisted XML. A test is added to make sure we can still read back such an XML.
updated changelog as a part of the release
merged back the RC branch
creating an RC branch
the trunk is toward 1.523-SNAPSHOT
Update stale javadoc

- The caller is no longer responsible as the listener is actually invoked from the method
[FIXES JENKINS-2494] Restore correct behaviour

- Fixes a regression in core where the display name clear on copy was triggering a save
- More than one way to do this, could also have used the marker interface approach
  This route seems slightly less fragile, though people could still add ItemListeners
  with order == -Double.MAX_VALUE which would then introduce intdeterminism.
  A marker interface would remove that indeterminism as the onCopyComplete method would
  be only called on the Job as the last method... but it could be hard to
  ensure that all ItemGroupMixin's respect the calling of onCopyComplete contract
  hence this approach seems better to me for that reason