ramanathan1504 opened a new pull request, #4315:
URL: https://github.com/apache/logging-log4j2/pull/4315

   `log4j-core-test` had one class directly in `org.apache.logging.log4j.core`, 
the package `log4j-core` also exports. JPMS forbids reading one package from 
two modules, so a   
     consumer requiring both fails:                                             
                                                                                
                   
                                                                                
                                                                                
                   
         module org.apache.logging.log4j.samples.nashorn reads package          
                                                                                
                   
         org.apache.logging.log4j.core from both org.apache.logging.log4j.core  
                                                                                
                   
         and org.apache.logging.log4j.core.test                                 
                                                                                
                   
                                                                                
                                                                                
                   
     That is what fails `integration-test (3.0.0-SNAPSHOT)` on 
`log4j-nashorn-test`. `2.x` has no class in that package.                       
                                    
                                                                                
                                                                                
                   
     The class only touches public API and reaches `resetThreadContextMap` by 
reflection, so the placement is vestigial. One call site, updated here.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to