As of 2016-03-18, the JDK module graph contains modules called jdk.jvmstat and jdk.jvmstat.rmi.

The names jdk.jvmstat and jdk.jvmstat.rmi imply "API for accessing JVM stats locally" and "API for accessing JVM stats remotely", but neither is true. There's no usable API in the former module (all its exports are qualified to other jdk.* modules) and there's only a tool in the latter module. Our convention for JDK module naming suggests "internal" in the former's name and "jstatd" in the latter's name.

Furthermore, the jdk.jvmstat module is dominated(*) in the module graph by the jdk.attach module. This suggests that rather than renaming jdk.jvmstat to jdk.internal.jvmstat, it should simply be folded into jdk.attach. jdk.attach would gain some qualified exports to its direct consumers.

(*) Truthfully, there is one module which requires jdk.jvmstat without going through jdk.attach: jdk.jvmstat.rmi. Happily, there is no conceptual or technical problem with jdk.jvmstat.rmi depending on an enriched jdk.attach.

Proposal:
- Merge jdk.jvmstat into jdk.attach.
- Rename jdk.jvmstat.rmi to jdk.jstatd, and make it require jdk.attach.