Update jfr-events module to follow style guide #364
                
     Closed
            
            
          
  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.
  
    
  
    
Updated the jfr-events module to comply with the OpenTelemetry Java Contrib style guide requirements with minimal changes:
Changes Made
Test method visibility: Removed
publicmodifiers from test methods inJfrSpanProcessorTestto follow the style guide requirement that test methods should be package-protected rather than public.Static import alignment: Updated the static import in the test class to use the recommended
org.assertj.core.api.Assertions.assertThatinstead oforg.assertj.core.api.AssertionsForInterfaceTypes.assertThatas specified in the style guide.Validation
./gradlew spotlessCheckThe changes are minimal and surgical, addressing only the specific style guide compliance issues while preserving all existing functionality. The module's public classes were already properly declared as
finaland other style guide requirements were already met.Fixes #363.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.