ThomasReinhardt commented on pull request #8:
URL: 
https://github.com/apache/maven-toolchains-plugin/pull/8#issuecomment-1055204424


   This plugin is already threadsafe (see below). It probably was since a very 
long time but nobody cared to investigate. This change is only marking the 
plugin as threadsafe. It changes absolutely nothing execution-wise.
   
   Why do I think it is threadsafe? As I wrote on the jira page it does not 
hold any state and gets instantiated PER_LOOKUP. So there is no way it can 
share state across instantiations. Which also means there are no collisions, 
races etc. In fact, the plugin should most likely be optimized, because now 
every invokation reads toolchains.xml which is quite inefficient. But it is 
threadsafe and this is what this PR is about.


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to