This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
jmx is in the experimental config but jmx.common is not. Please fix.
What are the steps needed on engineering side to fix this problem. We do have now 2 modules depending on jmx.common: jmx and jconsole. I guess that he same problem exists for the jconsole plugin. The script that is making this check needs to be updated to reflect jmx module split.
The script making the check is fine, and it correctly determined that there is a real error in the update center. The stable UC, as defined in nbbuild/cluster.properties#nb.cluster.stableuc, lists the jmx module but not the jmx.common module. Clearly someone trying to get the jmx module from AU would fail since no jmx.common module is available. You just need to add jmx.common to stableuc and verify the fix in the next javadoc-nbms build.
Marking P1 since it is not just a test failure; the module cannot be used from AU until fixed.
I Added jmx.common and jconsole to the list of modules.