Hey Jason, Comments inline... By the way, Great Work! The Jakarta effort has taught me sooo much!
--- Jason van Zyl <[EMAIL PROTECTED]> wrote: > 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. > Cool. So I am looking at Maven from the perspective of building a tool to quickly develop web applications. > > 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. > The scripts are hard coded to point to jakarta.apache.org. I thought it would be nice to be able to override this value and point one's own repository. > > 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. > I tried an ant maven:metrics and it does a compile based on the dependencies, however in the web applications we develop I also want to include all the jar files defined in WEB-INF/lib on the classpath for the compile. I put my reference to the lib jars in the jarResources tag? > > 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. > Hmm.. I see you point here, and I agree with the strategy however for my purposes the defined directory structure is not compatible if you want to develop inside of a tomcat webapps directory. Take Care Jason Kary > 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]> > __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
