Would it make more sense to reject running // build or fallback to
sequential execution (with a warning) if any of the mojos bound to
lifecycle is NOT marked as thread safe? Personally, I'd hate to have
intermittent build failures.
--
Regards,
Igor
Kristian Rosenvold wrote:
I found the bug in th
I figured I'd make individual issues on the plugins and commit the
fixes, the plugin issues I've found so far are
reasonably small and I do not see the need for a high-level issue. (As
long as it's trivial stuff I'll just
make these commits without further ado).
We might need some kind of way t
Do we have any top-level jira for thread-safety and // build issues ?
I myself got failures in // build with AspectJ plugin
2010/4/12 Kristian Rosenvold
> I found the bug in the modello plugin that was breaking /any/ build using
> modello in multi-modules; and I'm fairly sure the same kind of is
I found the bug in the modello plugin that was breaking /any/ build
using modello in multi-modules; and I'm fairly sure the same kind of
issue will be found elsewhere:
Quite simply the mojo's use plexus components that are singletons but
the mojos themselves contain per-request mutable state
