Felix Meschberger wrote:
This all is actually the reason, why do not overwrite at the moment.
We could of course add a setting to force overwrite:
<Sling-InitialContent>
/content;overwrite:=true
</Sling-InitialContent>
Without this setting (or having it set to false), content is never
overwritten.
Hmpf, you beat me by 10 minutes :) I just wanted to come up with the
same idea :(
I assume, it's possible to specify several paths, like:
<Sling-InitialContent>
/content,
/resources;overwrite:=true
</Sling-InitialContent>
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
