That’s what I thought too, but it doesn’t seem to be the case. I would expect ‘rEx’ is simply root cause first, and maybe another pattern like ‘xrEx’ for root cause first and packaging information but there isn’t such pattern.
On Wed, Sep 12, 2018 at 4:54 PM Remko Popma <remko.po...@gmail.com> wrote: > Just looking at the docs I thought that adding the packaging information > was a feature of the ‘xEx’ layout pattern, not ‘rEx’. > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Sep 13, 2018, at 8:16, Kevin Jung <mykevinj...@gmail.com> wrote: > > > > Hello, > > > > I wanted to log the root cause first in the exception, so trying to use > > *rEx* in the pattern layout. However, it seems to log class packaging > > information as well, e.g. [spring-webmvc-4.1.5.RELEASE.jar:4.1.5.RELEASE] > > in the following example: > > > > at > > > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:943) > > [spring-webmvc-4.1.5.RELEASE.jar:4.1.5.RELEASE] > > at > > > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:877) > > [spring-webmvc-4.1.5.RELEASE.jar:4.1.5.RELEASE] > > > > Is there anyway to not include the packaging information with rEx option? > > I debugged into RootThrowablePatternConverter, but couldn't find anyway > to > > avoid. > > > > If there is no such option, then I will have to live with it. But I > would > > prefer to not have the packaging information if possible. > > > > Thanks, > > Kevin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
