On Wed, Jun 4, 2014 at 12:08 PM, Jim Garrison <[email protected]> wrote:
> Consider the phrase "...you have wandered off The Maven Way™". I can't > tell if you intended this ironically or seriously. If it's the latter, it > seems like you're saying is "Maven is perfect. If Maven doesn't handle your > use-case, then your use-case is invalid". Is that true? > Just observing this conversation. The so-called Maven Way™ can probably be reduced to: favor new plugins over more XML in your pom.xml files. I think (my interpretation only; this and $4 will get you a cup of coffee) this is because at least originally—and for what it's worth it still seems this way to me—your pom.xml is supposed to be a declarative object model. It's not really a place for stitching together plugin executions. The thinking is (again, for better or worse; don't shoot the messenger) that if you have some sequence of events that must take place at a particular point in the lifecycle, then encapsulate that sequence of events into a plugin and bind it once. Of course that presupposes a certain amount of ease-of-software-reuse in the plugin ecosystem—i.e. that it's brain-dead simple to write a plugin that combines other plugins—which may or may not actually be true depending on how the to-be-combined plugins were actually authored. Best, Laird -- http://about.me/lairdnelson
