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. > > 2) The other issue is the the way Gump embeds projects inside one > > another. Currently Maven depends on GNU regexp (we're working on > > removing it) and wanted to know if a project descriptor could be setup > > this instead of embedding the project definition. The same issue is > > present in the Turbine 2.x descriptor (webmacro, freemarker, helma > > xmlrpc) So can I break out the embedded projects and make descriptors > > for them that live on their own? So that they can be reused? I want to > > add support back in for webmacro and freemarker in Turbine 3.x so I > > would rather not define the project in each project. I assume I can just > > break them out. > > I don't follow. Can you provide an example? > > >http://cvs.apache.org/viewcvs/jakarta-alexandria/proposal/gump/project/jakarta-turbine-2.xml?rev=1.12&content-type=text/vnd.viewcvs-markup > > If I were to create dependency on webmacro in turbine 3 I don't want to > replicate the project entry that is embedded the turbine 2 entry. If > that embedded entry becomes globally available that's unintuitive so I > would like to not be in the habit of embedding projects in one another. > I think if there is a new dependency introduced it should be made into a > descriptor of its own right off the bat. Some cvs modules contain multiple projects. jakarta-commons and jakarta-commons-sandbox are prime examples. When one has a dependency on commons-util, one shouldn't care whether the dependency is satisified from one or the other. Another example in reverse is xml-xerces, when one shouldn't care whether this is satisfied from the xml-xerces cvs module or the xml-xerces2 cvs module. In this case, the code for webmacro is contained within the turbine 2 project in the form of a checked in jar. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
