rmannibucau commented on pull request #578: URL: https://github.com/apache/maven/pull/578#issuecomment-939739225
@michael-o yes, the fact it handles concurrency=1 to fall back on the well known and used behavior is a clear important step and the lock solves the original issue I think - I don't see a broken case like that at least. The thread local was creating bugs in mojo, inherited or not (even if both didnt have the exact same) so better to not try it further IMHO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
