The solution to
MPIR-322 as it got committed is incorrect in my opinion
+1, it's not the perfect and most generic solution
things like mvn package|install|deploy clean site
cleaning after compile then generating site is just a proof of the "it's not ideal" concept: but who wants to do that, not only to show that the
MPIR-322 solution is only a workaround for core limitations?
The same problem exists for artifacts not installed locally
+1: I never said
MPIR-322 is perfect
a plugin can't fix a core issue: it only can sometime workaround it, like the great idea in
MPIR-247 after fixing MNG-5568
the more I work on m-site-p (and I really mean work on it), the more I see the limitations we have in Maven core for really supporting a lot of things such a plugin require, ie coordination of plugins in a lifecycle parallel to the standard build lifecycle to summarize the whole idea
But m-site-p works not so bad for a long time
Then even if I know that there are strong limitations that will require strong changes in Maven core, we'll have to live with limited workarounds to extend the "m-site-p works not so bad for a long time" mantra as much as possible instead of focusing only on "there are strong limitations that will require strong changes in Maven core"