> -----Original Message----- > From: Sam Ruby [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 10:29 AM > To: Alexandria Developers List > Subject: RE: problems w/ gump > > > Scott Sanders wrote: > > > > I do feel that the <cvs/> element belongs in the <module/> element, > > but I *hate* the fact that the project is not explicitly > saying that > > it depends on it. Not all projects defined in a module > depend on the > > <cvs/> being executed. This is want I want to fix eventually. > > How much more explicit then ENCLOSURE can you be? ;-) >
The problem is that the enclosure is not correct. http://cvs.apache.org/viewcvs.cgi/jakarta-alexandria/proposal/gump/proje ct/xml-cocoon2.xml?rev=1.43&content-type=text/vnd.viewcvs-markup Shows this: <project name="jisp"> <url href="http://www.coyotegulch.com/jisp/"/> <description> Java Indexed Serialization Package </description> <home nested="src/scratchpad"/> <jar name="lib/jisp_1_0_2.jar"/> </project> Does the jisp project depend on the cvs element from the xml-cocoon2 module? I would think not. Scott > Here's a simple rule: "projects depend on the cvs sources > from the modules which contain them." Makes sense to me. > > If vindico were to internally generate virtual project > definitions from module definitions which contain <cvs> > elements by taking the name of the module and appending > "-cvs", and adding the dependencies which are implied by the > above rule, then we could stay with the current project definitions. > > Make sense? This all makes sense, as long as we handle what I have mentioned above. Scott > > - Sam Ruby > > > -- > To unsubscribe, e-mail: > <mailto:alexandria-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
