JDK-8167485 : Integrate new version of Java VisualVM based on VisualVM 1.3.9 into JDK
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
VisualVM 1.3.9 was released on October 4th, 2016
Java VisualVM binaries (based on VisualVM 1.3.9) need to be integrated into JDK.
I can't yet. This fix is targeted to 8u151, Oct CPU. We won't have a first build of this, and thus a new payload manifest, for like 6 months.
I see the critical request for April CPU, 8u131. But until it makes it in a promoted build, we don't have a manifest to make our changes off of.
Here is an example of an Install SQE test manifest change. The change itself is not related to this bug:
I think there is some confusion with this bug since it touches several different components.
Paul K (Install Dev) gave the critical request justification. In those cases, it falls to Install SQE to given an OK based on that justification. Which I did.
I realize now that this bug touches several components. It is unusual for a "tools" bug to get a justification from the Install dev. That threw me and caused confusion. I gave a component-wide SQE-OK to a bug that I should not have in this case.
My "OK" was from an Install SQE perspective only. Other SQE components need to do their own eval.
Install SQE OK with critical request. No new test dev needed on Install SQE side.
Other SQE comps (tools, vm, etc) need to evaluate.
Unless I am missing something, from an Install testing perspective this just amounts to new files in the install payload manifest. There is no new Install functionality to test. When this change is integrated we will check and adjust our payload expectations. The payload manifests are checked during almost every automated install test.
Short answer, all our existing tests will already test that the new files are delivered by the installer, and check for regressions that may be caused by it. Any functionality beyond that is beyond the scope of the Install component.