Hi, management or development or both?
BTW, I'm not trying to start a flamewar, I think maven is a superb idea. I just wanted to open the debate about the different ways maven could be used, and how to make maven applicable to as many developers as possible? Quote from maven overview "Maven aims to make the developer's life easier". I reckon much of the work in maven is aimed more at the management of projects, whist the functionality to aid development falls short of what a developer routinely needs. I think that a typical development day a developer could make code changes and want to see them in a deployed environment 100+ times a day. At the same time they might be less interested in creating javadocs, task lists, changelogs etc. (IMO) These sorts of tasks (whilst important) could/should be run automatically on a centralised build box. e.g. It feels to me that maven is half way there with the j2ee plugin build scripts - automating the building of war files etc, but falls short at the deployment stage. If maven were to manage the whole of the build / deploy / test cycle, I think would increase the usefulness of maven to developers, therfore increasing adoption of maven. e.g. as a developer I'm interested in comiling my changes as quick as poss, so watching the build process spending half of its time checking pom-updates etc is phaps not what I want. cheers Nathan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
