Stephen Connolly wrote: > https://cwiki.apache.org/confluence/display/MAVEN/Dynamic+phases > > Thoughts?
Very nice. I like this a lot. In particular, it still feels like Maven with its well-known phases rather than like the "every project rolls their own" approach of Ant or Gradle. And to answer one specific question from your proposal: "Do we need a differentiation between validate and initialize?" I would argue that the answer is Yes; the two phases are for different things. To initialize I would bind something like buildnumber:create or pretty much all of the build-helper-maven-plugin's goals. My intuition would be that the initialize phase is where you programmatically augment the project model. In contrast, the validate phase is for validating your input (or environment). Now in the common case (Java), inputs are already validated by the compiler, but if my compile goal is xml:transform, then it makes sense to have xml:validate bound to the validate phase, as XSL Transforms typically don't check that diligently that their input adheres to some expected format. (It also makes sense to bind xml:validate bound to test or verify, too, to check the output's format.) Just my 2 cents. But overall, a really nice proposal. Best wishes, Andreas
signature.asc
Description: OpenPGP digital signature
