On Sat, 2002-03-16 at 10:20, Jason Kary wrote: > Hi, > > If I understand the concept of Maven correctly, then I believe it is a > framework for setting a common development environment for a new > project. Is this correct?
This is part of it. A common development environment, development strategies, tools for publishing your site, metrics and massive building including the idea of continuous integration. > Here are some thoughts I had will trying to use Maven for a generic > project creator for building Web Appliations: > > 1) Have the jar datasource for the "get" command defined in project.xml. Not sure what you mean here. The jar files pulled down via http are defined in the project.xml file in the <dependencies> section. > 2) Have the <jarResources> included in the classpath for compiles. Ok, do you have a use case for this? Suggestions with examples would help elucidate your point. > 3) Have the ability to define you desired directory structure in the > project.xml -1 The structure will be the same for all projects so that someone who is familiar with one 'mavenized' project will be familiar with all 'mavenized' projects. The goal is to try and unify all aspects of development and this includes the project structure. We will eventually have tools to help people migrate their projects. I really don't see having a set structure as being that terrible. > Will the default.properties used by most of the jakarta projects go away > with this system? It seems most of the stuff in default.properties can > be derieved from project.xml. I'm not counting on Maven being very popular with other Jakarta projects. I just wanted to try this with Turbine first. > Thoughts? > > Jason Kary > > > > -- > 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]>
