I know you guys are pretty swamped but I think this one is important... when a non-maven user tries to build using maven and they get a stack trace like that, they immediately turn off even if it's a simple fix; they miss the message about what needs fixing because it off the screen, or there is a stack trace on the screen that is not relevant to whats happening.
I think (I beg) that before you release version 1.0, you need to do something about those useless (from the user point of view) stack traces. Ant does this fairly well by keeping the stack trace short, or actually telling you what the problem is.
At the very least you can chop the bottom of the stack trace off and only show me the relevant trace, because myself and my peers don't care what the internals of Maven look like... we only care that we can't build our own tree and we need to know why quickly and clearly.
- Brill Pappin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
