I have been able to make unit test which reproduces the false warning. And I
have fixed the way the classloader was created. Thanks for the insights.
Nicolas
> Le 13 avr. 2018 à 07:38, Stefan Bodewig a écrit :
>
> On 2018-04-12, Nicolas Lalevée wrote:
>
>> As far as I can
On 2018-04-12, Nicolas Lalevée wrote:
> As far as I can see, the classpath used by checkForkedPath is the
> proper one. The function which manipulates the classpath to add the
> Ant runtime [1] is called before. So I should start looking into the
> AntClassLoader which is improperly finding the
> Le 12 avr. 2018 à 16:57, Stefan Bodewig a écrit :
>
> On 2018-04-12, Nicolas Lalevée wrote:
>
>> The Junit task is printing a warning if it finds multiple versions of
>> Ant in the classpath of the unit tests. It seems it doesn’t do
>> correctly the job if the ant
On 2018-04-12, Nicolas Lalevée wrote:
> The Junit task is printing a warning if it finds multiple versions of
> Ant in the classpath of the unit tests. It seems it doesn’t do
> correctly the job if the ant runtime is explicitly removed from the
> classpath.
Quite possible.
> Here the function