Summary: The org.openjdk.jmc.flightrecorder.configuration bundle contains many classes useful for working with jfr, and would be a great asset to have in core. It doesn't have any dependencies, so it shouldn't be too difficult to manage.
Additionally, there are a number of configuration-related classes that would be great to have in this bundle and could be incorporated at the time of migration. This includes:
- There are 12 classes that relate to JFC and XML grammar and validation, and these are not ui dependant like the classes in o.o.j.f.c.ui.configuration.model.gui so they can be moved safely
- It would be nice to have VolatileStorageDelegate in the core bundle, as it's a read-only template. Additionally it would be nice to have EventConfiguration, but this has a dependency on rjmx.services.jfr which is not an easy movement of code.
In total, in addition to stock flightrecorder.configuration in core we'd also contain (13):
I have a branch where I have series of wip commits that accomplish this, and it seems to be working well at the moment: https://github.com/aptmac/jmc/tree/flightrecorder-configuration-to-core
The migration of flightrecorder.configuration is also required for rjmx classes to be moved to core, as tracked by https://bugs.openjdk.java.net/browse/JMC-7069