(Apologies in advance if this message doesn't thread correctly)
> Given that DefaultLegacySupport is already marked Singleton, could the
> static ThreadLocal be replaced with a final AtomicReference instance field?
> This would be accessible across all threads, has less chance of leaking and
> can
Hi,
I have encountered an issue similar to MNG-4785 [1] while using plugins
from Eclipse's Tycho project, where code running in a worker thread of
Eclipse's job framework uses LegacySupport to get the current Maven
session. It is used for artifact resolution [2], just like in the ticket.
This work
