This might be under your category of "lack of good documentation": the tool really doesn't help you determine what's happening.
The error messages are obscure, and there is now easy way to determine what is even easily available from the command line. To learn anything about maven, you need to be dedicated to really wanting to use it and be willing to dive into online documentation. The "Better Builds with Maven" online book was a huge benefit - we are making the switch for some projects, and we never would have been able to enable that without the online book. -joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Redmond Sent: Tuesday, August 29, 2006 10:55 AM To: Maven Users List Subject: [POLL] Why switch to Maven? Hi all Maven users! I'm beginning a study to outline the real reasons that people have for avoiding Maven. My questions to you all are: What were your anxieties about using Maven? If you use Maven: what helped you make the decision? If you don't: why did you avoid it? Here are some that I have heard in the past: * Lack of good documentation. * Community unwilling to help me with my problems. * Not "industry supported" or "mainstream" enough. * I don't like conforming to the Maven project layout. * My project is too complex to switch. * There are not enough plugins available. * We already have a large investement in tool X. * I have to build native/non-Java code. Any more reasons? Care to expand these ideas? Thanks for your help! ____ Eric Redmond http://codehaus.org/~eredmond --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]