[JENKINS-14585] MavenTestDataPublisher didn't do anything
must continue and not return, if a single module has no SurefireReport
bug fix
bug fix
(cherry picked from commit d8f74cf86644ff338aff53879f674b971c11967e)
more bug fix
check name conflicts in local ItemGroup
grunt profile to run grunt for web resource optimization
Updatign tests
[FIXED JENKINS-18585]

The earlier fix by @ssogabe broke the test. This fix corrects the
problem properly.

The reason this error happens with some plugins is that if there's an
input field whose name is "on", then even after prototype.js extends
an element object, "form.on" will refer to the input element, not the
prototype.js function to add an event handler.
Ignore generated files
Fixed deadlocks that I started observing a lot during releases
added l10n(ja)
Merge pull request #810 from kutzi/claim-plugin-fix

[JENKINS-14585] core side fix for: claim-plugin cannot claim broken tests in maven jobs
[FIXED JENKINS-14585] Noting
This helps a lot when mocking AbstractProject in unit tests, because so I don't have to suppress the constructor with PowerMockito
fixed some warnings
[maven-release-plugin] prepare release jenkins-1.522
[maven-release-plugin] prepare for next development iteration
updated changelog for release
updated changelog as a part of the release