There are a few places in code, where manual `for` loop is used with Iterator to iterate over Collection. Instead of manual `for` cycles, it's preferred to use enhanced-for cycle instead: it's less verbose, makes code easier to read and it's less error-prone. It doesn't have any performance impact: javac compiler generates similar code when compiling enhanced-for cycle. Similar cleanups: 1. [JDK-8274016](https://bugs.openjdk.java.net/browse/JDK-8274016) java.desktop 2. [JDK-8274237](https://bugs.openjdk.java.net/browse/JDK-8274237) java.base 3. [JDK-8274261](https://bugs.openjdk.java.net/browse/JDK-8274261) jdk.jcmd
------------- Commit messages: - [PATCH] Use enhanced-for instead of plain 'for' in java.management Changes: https://git.openjdk.java.net/jdk/pull/5695/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=5695&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8274318 Stats: 16 lines in 3 files changed: 0 ins; 7 del; 9 mod Patch: https://git.openjdk.java.net/jdk/pull/5695.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/5695/head:pull/5695 PR: https://git.openjdk.java.net/jdk/pull/5695