Small project, large project, small team, large team, maven is applicable to all.
If you've never used maven, creating a parallel build for an existing small project is a great way to learn IMHO. If you like maven and it makes your life easier, then you can deprecate the old system. Think of it as "Build Refectoring" Good luck and ask plenty of questions when you need a hand, Doug On 9/5/06, Sha Jiang <[EMAIL PROTECTED]> wrote:
Hello, Maven can adapt various projects. But in my eyes, it's not necessary to use Maven in simply projects. In fact, most projects don't use Maven. Small project may not include many modules, and there are few the developers. Then using Maven makes a bigger complexity and redundancy possibly. a cup of Java, cheers! Sha Jiang 2006/9/5, Alexander Sack <[EMAIL PROTECTED]>: > > What do you mean? Can you explain why you think it wouldn't be? > > My biggest draw to Maven right now is the dependency management and > inheritance capabilities. Especially in a Java EE centric world where you > have the concept of client side jars, runtime dependent libraries, as well > as provided/platform libraries. Its hard to manage this with just > ANT. Add > Eclipse, and things become even more complicated. > > Bottom line is its not the number of people on the project that determines > Maven's usefulness, its the project itself. > > -aps > > On 9/5/06, Dudu <[EMAIL PROTECTED]> wrote: > > > > Is maven good to small teams, like two programmers? > > > > > > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > >
