Sorry it took me so long to get around to it.
> On Mar 21, 2018, at 20:59, Apache wrote:
>
> Obviously I didn’t see Remko’s reply before sending mine.
>
> Ralph
>
>> On Mar 21, 2018, at 4:57 AM, Apache wrote:
>>
>> Please do. Thanks!
>>
>> Ralph
>>
>>> On Mar 20, 2018, at 11:20 PM, Atle
Obviously I didn’t see Remko’s reply before sending mine.
Ralph
> On Mar 21, 2018, at 4:57 AM, Apache wrote:
>
> Please do. Thanks!
>
> Ralph
>
>> On Mar 20, 2018, at 11:20 PM, Atle Tokle wrote:
>>
>> I made a fresh clone from master today, and looked into it myself.
>> In CommandLineHelpTe
Please do. Thanks!
Ralph
> On Mar 20, 2018, at 11:20 PM, Atle Tokle wrote:
>
> I made a fresh clone from master today, and looked into it myself.
> In CommandLineHelpTest.java all the tests that is failing is instanciating
> a Help class. In all cases it have an alternative constructor where yo
These tests have been removed.
On Wed, Mar 21, 2018 at 7:39 PM, Remko Popma wrote:
> We will probably just remove these tests; there is no need to bring the
> picocli tests in to the Log4j2 project.
>
> On Wed, Mar 21, 2018 at 3:20 PM, Atle Tokle wrote:
>
>> I made a fresh clone from master tod
These tests have been removed.
On Mon, Mar 12, 2018 at 10:58 AM, Remko Popma wrote:
> Matt is right on all counts. The tests can be removed since picocli is
> tested in its own project, and when we split the modules it can be moved
> out of core into the tools module.
>
>
>
> > On Mar 12, 2018,
We will probably just remove these tests; there is no need to bring the
picocli tests in to the Log4j2 project.
On Wed, Mar 21, 2018 at 3:20 PM, Atle Tokle wrote:
> I made a fresh clone from master today, and looked into it myself.
> In CommandLineHelpTest.java all the tests that is failing is i
