On Sun, 2002-02-24 at 02:43, Peter Donald wrote: > Hi, > > I haven't actually looked into doing this just yet and I was hoping someone > could give me a rundown on feasability before I looked into this. > > Basically what I want to do is have the possibility of a project file stored > in CVS of each module. So gump/projects would basically just include the > module information and possibly the name of project descriptor in the CVS. > > Possible or not? Lots of work or not?
I pulled Maven from the alexandria repository and it is now within the Turbine family of projects for the time being but I have the Maven build completely keyed a project descriptor. The Maven and Gump descriptors are not the same as I feel for a project the current Gump layout isn't quite right which I will definitely explain as the documentation builds for Maven. The basic upshot is that if a project builds using its Maven descriptor then it is guaranteed that the Gump descriptor will be correct. The responsibility of correctness is therefore offloaded to the project and this whole process of massive builds becomes managable i.e. one or two people are not responsible for trying to keep a whole raft of descriptors correct for building. The transformation I have is making a Gump descriptor but I have to add all full traversal of the dependency graph and place indirect dependencies in the Gump descriptor as well. This is how I plan for Maven and Gump to cooperate, and how this will actually make Gump's life a lot easier. Right now everything that you find here: http://jakarta.apache.org/turbine/maven/ Is built, tested with documentation generated from this single file: http://cvs.apache.org/viewcvs/jakarta-turbine-maven/project.xml?rev=1.3&content-type=text/vnd.viewcvs-markup I have lifted bits out of cactus to automatically upload all the documentation, and I have the source code cross referencer working with Maven's project object model. I think that a common build system can be used for all projects. Right now Maven bootstraps itself generates its own build system and everything you see on the Maven site is a product of that build system. This is an attempt get a grip on the Turbine projects as the decoupling of all the components has taken its toll on our ability to manage all the new bits. I have incorporated Ceki's dirlayout document, I plan to add aspects of Berin's common build file format though I have expanded upon it and I would like to use Morgan's release howto as a guide for versioning and JAR naming So it's completely possible and what I was going to ask from Sam was for conduit to Gump. I would like to add a target to the common build file that will transmit the Gump descriptor to a build box like the covalent machine. Once the project is built then you know the Gump descriptor is at least correct in form. Gump can figure the problems with compatibility in HEAD. I am planning to build something called a reactor that will do massive builds but my bent is not quite the same as Sam's which I am going to try and explain in the Maven docs today. > -- > Cheers, > > Pete > > ------------------------------------------------------------ > I just got lost in thought... It was unfamiliar territory. > ------------------------------------------------------------ > > -- > 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]>
