famod commented on pull request #655: URL: https://github.com/apache/maven/pull/655#issuecomment-1008786157
> With Guillaume's comment it looks like the warning can just be dropped at runtime and should be moved to plugin developer side only if not explicitly set so users will be happy whatever the plugin dev did, no? AFAICS, you could still hit concurrency issues in a plugin is executed concurrently for _different_ modules in the reactor. The commit @gnodet referenced is about project/module scoped locking if I'm not mistaken. -- 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]
