On Fri, 2002-06-07 at 05:48, Nathan Coast wrote: > Hi, > > management or development or both?
Both and more. Eventually the entire lifecycle of a project. To attempt to collect any and all documentation on best practices that concern all aspects of the development cycle and attempt to produces tools that make those best practices readily available and easy to use in practice. > 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? What is essential for widespread use is supreme ease of use. Jon's auto-installer idea is one I'm pursing. You should be able to checkout a project, run target (or command) and maven auto-installer should ask you a few questions and that's it. Currently the IA installers suck and I will probably remove them. Secondly we have to try and collect as many guides for development that we can because there are so many and make tools for effectively allowing developers to easily implement those guidelines. > 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. What does a developer routinely need? If there are pieces that are missing then lets fill that gap. > 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. They certainly can be! There is a tool called the reactor which a critical piece of Maven but it's one of the trickiest bits to get working. The start of the reactor is in the repository but I'm working on a couple bootstrapping problems before I try to check it all in and say that it's working. But the reactor is the tool that will allow automated processes to be executed on N number of projects where dependencies are automatically computed among projects. > 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. The documentation deployment is fully there. The distribution deployment is not quite there yet but will be and it has been thought about. > 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. Yes, with Ant we are going through a lot of crap in order to effectively use an object model. We are trying to correct this deficiency by using Jelly: so that we can use an object model and not have it take 20 seconds to build something. I don't want to use the XML directly as the POMs may be stored in any number of places eventually. Especially on a centrally located build box that manages hundreds the building of hundreds of projects. There is the musings file so feel free to add any thoughts you have to that file. I don't know about others but I look at that file often. > cheers > Nathan > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
