On Mon, 2002-02-25 at 14:11, Sam Ruby wrote: > Jason van Zyl wrote: > > > >>> I'm not sure I follow here: you want maven to build so that it can > >>> generate the gump descriptor? Just want to make sure I understand. > >> > >> You understand perfectly. > > > > Why is this necessary? A Maven project is just another build with > > another Gump descriptor, why does it have to be treated in a special > > fashion? > > I was under the impression that Turbine had a different format for > descriptors, and that Maven was required to do the conversion. Perhaps I > got that impression from the following: > > > This point will be moot once the Gump descriptor is created from the > > Maven project descriptor. They will always be accurate. > > If this step is not necessary, I would gladly dispense with it.
What does it matter if the descriptor comes from a patch that goes to the mailing list, a full submission or is generated? If you get the descriptor why does Gump need to know anything about where it came from? > >> In this case, the code for webmacro is contained within the turbine 2 > >> project in the form of a checked in jar. > > > > But if I wanted to list these projects separately with separate > > descriptor and make it a library generally available to the rest of > > projects that might want to build with it? > > Unless there is a bug that prevents it, you can do that today with the > current Gump. Jenny will do all the necessary sorting, merging, and > expansion, and dereferencing. Cool. > - Sam Ruby > > > -- > 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]>
