Deleting ancient cobertura profile, which was broken at least by Java 8 if not earlier. If we want code coverage we can use JaCoCo as plugin-pom does.

Translate into Simplified Chinese with creating new properties file

Only inspect direct subdirectories for Surefire reports

Document and refactor the CanonicalIdResolver extension point

Rethrow any kind of RuntimeException, such as errors from RobustReflectionConverter

[JENKINS-48080] Setup Wizard hangs if confirm password is incorrect while creating admin user

[JENKINS-34855] more AtomicFileWriter test harnessing

war/src/test/js/ apparently produces war/target/surefire-reports/JasmineReport.xml without the TEST- prefix used by Surefire.

* Use NIO for FilePath#chmod and IOUtils#mode

* Add tests for NIO mode and chmod implementations

* Add test, remove new method, and update JavaDoc

* Provide system property to use native implementations of chmod and mode

* Revert unrelated whitespace modification

* Don't remove exception from throws and put imports in original location

* Fix broken JavaDoc links

* Ignore file type bits (above 0o7777) in Util#modeToPermission

* Use octal for constants and don't include file type bits

* Revert unnecessary changes to TarArchiverTest

* Add assertion that non-permission bits are ignored by chmod

* Use NIO copy with StandardCopyOption.COPY_ATTRIBUTES in copyToWithPermissions where possible

* Catch InvalidPathException and convert it to IOException

* Create utility method for File#toPath and use File#createDirectories after review

* Remove useless calls to toAbsolutePath and getAbsoluteFile

* Fix typos and use octal for constant after review

* Add test for behavior of copyToWithPermission with special bits

* Add default implementations to deprecated methods of BuilableItem and Item.

Currently the interface requires the API user to implement already deprecated methods.
It does not make much sense, and the API could be simplified.

* Address comments from @jglick

[JENKINS-34855] AtomicFileWriter is not Atomic

The path could already exist, *but* not be a directory.
Nice catch James.

Associated tests.

Not that critical, but still can keep them as we should
generally be on FS that support atomic moves. Hence not
enter that catch.

If proved otherwise, we'll reconsider adjusting this verbosity.

[JENKINS-47429] User.getLegacyConfigFilesFor no longer seems to be necessary

* Introducing ItemGroup.allItems and similar default methods.

* Do not get me started.

If task can be run only on master, use shortcut