> Suppose maven was designed so that we could say "goal A's > input is the output of goals B, C, and D", instead of just "goal > A depends on B, C, D". <source>s would appear as input-less > goals, and most plugins would require output path properties, > not input path properties. Just a thought.
Make it a bit more explicit. A pipeline is not always a straight line, but can have a junction. Take AspectJ for example: it has two inputs and one output. The inputs are the sources and the aspects and the output is the folder with the aspects woven in the sources. Define for every plugin the inputs and the outputs, document a standard location, but give the opportunity to override these. For the rest, nothing but applause for the pipeline proposal. Ringo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
