<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 3, 2019 at 2:59 PM Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-family:"trebuchet ms",sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 2, 2019 at 12:40 PM James Perkins <<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Unfortunately we can't remove log4j support. We also need to support log4j v1 for legacy application support. We actually use a fork [1] of log4j which delegates the actual logging to the JBoss Log Manager.</div></blockquote><div><br></div><div><font face="trebuchet ms, sans-serif">That is a fork though; i.e. WildFly itself does not ship</font> log4j:log4j.</div><div><br></div><div>A number of our testsuite modules do declare log4j:log4j as a test dependency, but AIUI org.jboss.logmanager:log4j-jboss-logmanager is API compatible so is it possible to instead have the testsuite depend on the fork and eliminate this dependency?</div></div></div></blockquote><div><br></div><div>Yes the org.jboss.logmanager:log4j-jboss-logmanager can be used as a replacement of log4j. The only requirement is that the org.jboss.logmanager:jboss-logmanager also be on the class path. That is what we use with the shipped zips. We do not ship an Apache log4j library.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>[1]: <a href="https://github.com/jboss-logging/log4j-jboss-logmanager" target="_blank">https://github.com/jboss-logging/log4j-jboss-logmanager</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 1, 2019 at 2:03 AM Andrew Marlow <<a href="mailto:marlow.agents@gmail.com" target="_blank">marlow.agents@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello everyone,</div><div><br></div><div>I am trying to build the latest wildfly from a clone of the github repo at <a href="https://github.com/bstansberry/wildfly.git" target="_blank">https://github.com/bstansberry/wildfly.git</a>. I understand this is the latest and is from the principal maintainer, Brian Stansberry. I've changed the pom references to the old log4j-v1 to the new log4j-v2 but a pom dependency analysis reveals there is a still a dependency on v1. I am at a loss as to where exactly it is coming from. I hope someone here can shed some light please.</div><div><br></div><div>The relevant part of the dependency tree is shown from the extract below:</div><div><br></div><div>INFO [m] org.wildfly:wildfly-ts-integ-smoke:jar:19.0.0.Beta1-SNAPSHOT<br>INFO [m] +- org.jboss.ws.cxf:jbossws-cxf-client:jar:5.3.0.Final:test</div><div> :</div><div>INFO [m] | +- log4j:log4j:jar:1.2.17:test<br> </div><div>Initially I thought it might be coming via an old version of apache CXF but I see from the top level pom that version 3.3.4 is being used, which is the latest. Any ideas?<br></div><div>-- <br><div dir="ltr">Regards,<br><br>Andrew Marlow<br><a href="http://www.andrewpetermarlow.co.uk" target="_blank">http://www.andrewpetermarlow.co.uk</a><br><br></div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div>