Joern Nettingsmeier schrieb: [...]
> while we're at it: > > ./blog/config/ac/ac.xconf > ./blog/config/notification/notification.xconf > ./blog/config/publication.xconf > ./default/config/ac/ac.xconf > ./default/config/cocoon-xconf/instantiator.xconf > ./default/config/lucene_index.xconf > ./default/config/search/lucene-live.xconf > ./default/config/publication.xconf > ./default/modules/homepage/config/cocoon-xconf > ./default/modules/homepage/config/cocoon-xconf/resource-type-homepage.xconf > ./default/modules/defaultusecases/config/cocoon-xconf > > ac.xconf and notification.xconf should be renamed, +1 BTW, is "ac" obvious enough, or should we call it "access-control.xml"? > with lucene i'm not > sure - is this our code that reads the file or lucene's? I guess it's ours, but I'm not sure. > the use of .xconf vs. .xml is not really consistent anywhere... should > .xconfs be only files that are treated as xpatchfiles (with "unless..." > and friends), IMO yes. > or does it mean "xml configuration file". the latter would > be ok for pretty much everything... > > and one last thing: > > does anybody care about src/pubs/*/publication-tests.xml ? I don't. There should be a place for publication documentation, though, and the test scenarios could go there. Maybe something for 1.4.1. > it used to be aggregated with the old publication.xml file, but i did > not rip it out lest somebody was using it for automated testing > scripts... i'd like to get rid of it if nobody objects. +1 to remove it. -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
