You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use the resource optimizer plugin in parallel builds. This plugin is not explicitly marked as thread safe (or not thread safe). It would be nice if you could evaluate if this plugin is thread safe and mark it as thread safe (or not thread safe).
If it is not thread safe maybe you can give a statement if thread safety will come in a future release.
Best Regards,
Jens
The text was updated successfully, but these errors were encountered:
We use this plugin with Maven 3.x (and parallel builds) without problems. How can I mark this plugin as thread safe? Is it not automatically thread-safe when you use Maven 3.x? You are welcome to provide a patch if you have any. Feel free to send a pull request.
Hello,
Thanks for your fast reply.
I’ve send you a pull request. It’s just one simple line which can’t break the build. As far as I know parallel builds were not supported in Maven 2.
Maven 3 allows parallel builds but can’t guarantee that every plugin is executed thread safe.
Developers have to check manually if the plugin is thread safe and mark it to prevent a warning in parallel builds.
I think it’s really hard to evaluate if a plugin is really thread safe but nice to hear that you use it in a parallel build and everything works fine!
Best Regards,
Jens
We want to use the resource optimizer plugin in parallel builds. This plugin is not explicitly marked as thread safe (or not thread safe). It would be nice if you could evaluate if this plugin is thread safe and mark it as thread safe (or not thread safe).
If it is not thread safe maybe you can give a statement if thread safety will come in a future release.
Best Regards,
Jens
The text was updated successfully, but these errors were encountered: