Surely architecture should attempt to handle gracefully tasks that seem intuitive to the user but do not perform as expected.
A user creates a goal that calls two attainGoals, and these two attainGoals both call reactors that may share one or more sub projects. The build then fails with a very obscure error message. At the very least, this should be handled as an exception.
Now, I'm not suggesting that maven is badly architected. On the contrary, I will never go back to any other build/project management tool, but I do question this specific behaviour and whether it is being handled as well as it could be.
Jake
Andy Jefferson wrote:
A plugin performs a particular task ... whether it is a "core" plugin, or a plugin for an extension task is not important. "multiproject" is a core plugin. Maven provides its capability via plugins, rather than lumping everything in a big binary, so you can use what bits you want ... its called architecture.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
