[JENKINS-14585] MavenTestDataPublisher didn't do anything
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
If every node is restricted to tied jobs only, Matrix build jobs can never start.
Merge pull request #832 from stephenc/execute-flyweight-anywhere

If every node is restricted to tied jobs only, Matrix build jobs can never start
must continue and not return, if a single module has no SurefireReport
bug fix
check name conflicts in local ItemGroup
grunt profile to run grunt for web resource optimization
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
merged back the RC branch

Conflicts:
	core/src/main/java/hudson/model/AbstractProject.java
creating an RC branch