Hi, Reading through the code, I see that TraceFactory seems to initialize by default a Jdk14TraceFactory if there's none specified in the system property "org.aspectj.tracing.factory". This also means that you can override it and choose a different implementation.
Regards, Andrei On Fri, Nov 27, 2020 at 12:40 AM Eric B <[email protected]> wrote: > Hi, > > I've been forced to revisit a hackish approach that I put together to get > AspectJ working in Wildfly a couple of years ago, It led me to this ticket: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=502093 > > Looking through the code on github, I see that the Jdk14Trace.jav > <http://git.eclipse.org/c/aspectj/org.aspectj.git/tree/weaver5/java5-src/org/aspectj/weaver/tools/Jdk14Trace.java#n13>a > class is still in the master branch still leveraging the java.util.logging > classes. > > Has any work been done to address this? Is there any workaround that I > can apply to have the weaver defer using the logging subsystem until it > gets properly initialized in Wildfly? > > Thanks, > > Eric > > _______________________________________________ > aspectj-users mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/aspectj-users
