On Wed, 2002-03-13 at 07:40, [EMAIL PROTECTED] wrote: > Hi, > > I'm currently developing a build system handling several > modules/projects and dependencies between these modules. The build > system is based on ant. > > I found GUMP and it seems very similar to my approache, but I'm still > confused about what GUMP is. > Is is a framework or tool set (like ant) handling several modules and > their dependencies, a framework which can be downloaded, installed and > used for my own projects? > Or is it a web project (like Sourceforge) where I can "register" and add > my modules to a pool of projects? > > What I'm looking for is a framework or some tools which I can use for my > own project (my own nightly build etc.)? Is GUMP the right place to > start? I first started with ant, but ant doesn't support multiple > projects, does it?
You might want to take a look at Maven: http://jakarta.apache.org/turbine/maven/ It is currently a turbine sub-project but it provides all that you've mentioned above. The site mentioned above is where you can see all the things that Maven is currently producing for a project. Among some of the things provided: -> xref'd sources -> javadoc production -> site publication -> change log document produced from cvs log output -> source metrics -> standard build system that is generated and operates from a project descriptor so if the build works then the descriptor is correct In a very short period of time we have 8 developers who have either donated substantial pieces of code or have put in a lot of time to date. We have a full java parser that will be used for metrics which Stephane Bailliez is working on with myself (he's an ant committer), an RCS ,v parser which can be used to track CVS activity. Dependency resolution using the commons graph package which is about to be completely overhauled by David Peugh (author of the Quilt, the test coverage tool on SF which will be integrated into Maven). We also plan to make a tool like Cruise Control but that will be after the turbine release. Right now we are experimenting with the use of Maven on the Turbine projects. We are releasing 2.2b1 of Turbine this coming Monday and all the builds, and site publication will be controlled by Maven. Maven is also capable of producing Gump descriptors so you can work with Maven at the project level and participate in wider gump builds if you like. Take a look you might find something that you like. > Currently, I'm working on a system based on some XML files (and these > files are very similar to GUMP's project/module etc. XML files) which > are transformed to ant build.xml files. As far as I understand the FAQ > and the Javadoc, GUMP used this approach but changed from XSLT to Java? > Is there a little bit more documentation about GUMP? Maven takes a different approach where the project descriptor is actually used for building directly. > Regards, > > Jens > -- 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]>
