Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@open-telemetry/java-maintainers
I'd like to read a JFR file, convert it to OTel profiling format and export it. The JFR consumer API is 9+ only. As seen here, building the profiling exporter with 11 works for the single module, but breaks the parent :exporters:otlp:all build.
Any preference on how to change the build deps to support this without making the blast radius of the change too big? Worst case I can split the JFR layer of the export code off into its own module, but I'd prefer to keep it bundled with the rest of the profiling code. Thx.