On Wed, 2007-11-21 at 17:41 +0100, Jörn Nettingsmeier wrote: > Andreas Hartmann wrote: > > Jörn Nettingsmeier schrieb: > > OK, so how should this issue be addressed? > > > >> let's provide a real basic publication instead that doesn't have so > >> much cruft and can be used as a template for both the default and any > >> custom publication. > > > > Hmmm - how would that solve the problem that I want to override single > > pipelines? Or do you mean that the basic publication should be so basic > > that it contains virtually no pipelines which could be worth overriding? > > more or less, yes. i still think that no important functionality should > be embedded in the default publication sitemap. ideally, i'd like to be > able to create a publication directory with just a config dir in it, and > all central lenya features should be there.
Well, I must disagree. I had the same problem as Andreas have back in the days. To override just a pipe is much more efficient then copy one thing to another place. MORE if we talking about parent publications. The idea is to implement all pipes that are needed in the parent and allow children to override just a few of them. To put it in java terms the default pub should be an abstract class and every pub that extends the default pub should have the possibility to override super. salu2 > > for now, you could just copy the default sitemap over, throw out all > matchers that you don't need and alter it as necessary. > eventually, a feature as you describe might be interesting, but first we > should clean up and get a feeling for a nice minimal set of pipelines > that needs to be in a publication sitemap. to me, neither bxe nor dav > nor rss stuff qualifies. > -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
