> I'm not sure whether or not this addresses your concern, but > let me give > some background to the design of the data definitions used by > gump. The > way gump works is that definitions extend one another. So we > could start > with a base definition for what you would get if you simply > installed an > ant package. Another definition could add (extend or > subclass in OO terms) > the original definition to add build information. > > The only reason why the current xml files aren't factored out > this way just > yet is that gump hasn't yet attracted enough of a user community. > > > - I am afraid that by having local copies of project definitions > > (jakarta-ant.xml) you, in effect, get the same behavior of people > > maintaining versions of jars in CVS. > > Does the above answer help clarify?
Yes. Thank you for the explanation of the data model. -Naresh Sikha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
