[ 
https://issues.apache.org/jira/browse/LOG4J2-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372582#comment-16372582
 ] 

Andrejus Chaliapinas commented on LOG4J2-2266:
----------------------------------------------

Sorry for my unlear point about unit tests - those are mine for my project, 
using JUnit+Powermock combination. When Log4j2 v2.8.2 is in classpath - they 
work. When Log4j2 v2.10.0 - some of them fail with above error.

 

I didn't yet attempt to build master branch with JDK9 as according to Matt I 
could do rebuild with only JDK9 if I'd like to add some extra debugging/etc. to 
understand issue better myself. Curently I'm just using JDK8.

 

That's why my proposal is to introduce JDK8 compatibility setting, which will 
allow logic around ServiceLoader to work the way it was for v2.8.2 and leave 
JDK9 specifics aside and for those who really needs that/tries that. Does it 
make sense for you?

> Log4j2 throws NoClassDefFoundError in Java 8
> --------------------------------------------
>
>                 Key: LOG4J2-2266
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2266
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.10.0
>            Reporter: Andrejus Chaliapinas
>            Priority: Major
>
> During Unit Tests run using JDK 8 and Log4j2 v2.10.0 - getting this as part 
> of exception stack:
>  
> java.lang.NoClassDefFoundError: Could not initialize class 
>  org.apache.logging.log4j.util.PropertiesUtil
>      at 
> org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:71)
>      at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:60)
>  
> and issue seems to be somehow related to what is reported so far against JDK 
> 9 here: LOG4J2-2129.
>  
> If some patch on top of v2.10.0 is available to test - please let me know 
> where to download it from.
>  
> While running same UTs with same JDK 8 and v2.8.2 - issue is not observed.
>  
> And question which I have here - why not introduce JDK8 compatibility runtime 
> mode while things with JDK9 are not yet that stable? So it could continue use 
> same logic as of v2.8.2 around that ServiceLoader and not cause side effects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to