On Tue, Nov 11, 2008 at 5:26 AM, Brett Porter <[EMAIL PROTECTED]> wrote: > This sounds useful to try. > > There are two things I'd do if you're building this: > - be cautious about letting it get too complicated (trying to be everything > to everyone) > - break the parts out into components that can be reused (eg, IDE > integration). These could perhaps be brought back into Maven at some point > if we need settings file management beyond what is already there.
As a general rule, I find that people who use maven stay just as users. They just don't understand (and are even confused) by how it works even though it is simple to understand. The reason for this is that once maven has been setup it just works they dont have a need to increase their knowledge. Whereas those people who are users of Ant tend to have a greater technical understanding because they are forced to have this understanding. So for setting up maven in our company I just point them at our Wiki page. It describes: * how to download * how to install * how to configure * common trouble shooting steps And where necessary a boiler plate with "TODO" included where user specific data needs to be modified. However I find that most of the files can be copied verbatim and we have a complicated environment. I've yet to see any automated process return a better ROI than this simple process. And it is so different across environments that I can't see how a tool will help with the process. Unfortunately that means the local Maven expert has to set this up but its not much effort. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
