On 10 Jan 2003, David Crossley wrote: > Giacomo Pati wrote: > > Bert Van Kets wrote: > > > > > I did a completely new and fresh checkout of the CVS HEAD and can't build > > > it. It fails on a validation issue: > > > > > > validate-config: > > > [echo] Conducting validation of core configuration files. > > > [echo] (You can turn validation off if you must, using ./properties.xml) > > > [echo] Validating all cocoon.roles instances ... > > > > > > BUILD FAILED > > > file:C:/xml-cocoon2/build.xml:2412: There must be a file attribute or a fileset > > > child element > > > > I have that too, but wasn't able to check it out to an end. I can say so > > far that the jing task itself works when used in a separate build.xml > > file. > > > > As a workaround I've set validation to false. > > > > Giacomo > > I do not have any such problem. The above error message > seems to indicate that someone had removed the <fileset> > element from that <jing> declaration. With today's cvs > the build.xml is complete and validation is okay. > Would you please try again today and see how you go.
I still believe validation doesn't work under certain circumstances. I've build Cocoon on more than 5 independant machines recently (Linux as well as Windows) which none of them could validate by using "build installscratchpadwar". They all say what Bert was reporting above. Interesting is the following: If you do a "build validate-xdocs" all runs ok. If you do a "build installscratchpadwar" it fails. I haven't figured why it is differen. Will have to investgate. Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
