I'll point to the bottom of that page in the BeanJUnit4Runner class
which demonstrates how simple it was to integrate into JUnit. The next
phase's complicated part will be linking configuration files to bean
creation along with refactoring Configuration classes to use the new
APIs. I'll point to [1
I've gathered together all the working subset of where I'm at and
committed it to the newly created "mean-bean-machine" branch. There
are numerous TODO comments left in there, but after so long, I figured
it was more important to show a work in progress rather than continue
to vaguely talk about it
One of the more noticeable impacts it will have is the ability to
define all the various singleton objects and configuration-global
objects in a more consistent fashion. This sort of thing will come
during phase two where I integrate it into log4j-core as mentioned.
On Sun, 23 Feb 2020 at 15:06, R
Although I see what you are doing in the test it isn’t clear to me what impact
it will have on Log4j and plugins. I am looking forward to seeing examples of
that.
Ralph
> On Feb 23, 2020, at 1:22 PM, Matt Sicker wrote:
>
> Yes, the thing I've been talking about for the past few months, after
Yes, the thing I've been talking about for the past few months, after
several iterations and a couple rewrites, is almost ready for review.
In preparation for that, I've been refactoring the existing unit tests
based on my recently written JUnit 4 runner that handles automatic
dependency injection
