> On Jun 29, 2021, at 3:08 AM, Jaikiran Pai <jai.forums2...@gmail.com> wrote:
>
>
> On 29/06/21 12:34 pm, Jaikiran Pai wrote:
>>
>>
>>
>> > Out of all these 4 points, I think if point number 2 can be addressed such
>> > that it just prints only once the warning for each caller class, then the
>> > issue noted by users of Ant build file will be drastically reduced. I
>> > haven't yet tried or proved it, but I think we will end up with just one
>> > log message in their STDERR for the entire build for a majority of the
>> > cases. I will experiment with that this week to see if that's true.
>>
>> FWIW - I implemented a very primitive cache in the System class to log this
>> message just once and see if it helps for the general/regular usecase that I
>> used as an example.
>
> To be clear, just once for each caller class.
In your case, is the class always the same object? I was thinking about if I
should use a String or a Class<?> as the map key. Is it possible for the same
class to be loaded again and again?
Thanks,
Max
>
> -Jaikiran
>
