Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning
in the TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A long time
ago, we agreed that if we change the sitemap syntax, we
Carsten Ziegeler wrote:
A long time
ago, we agreed that if we change the sitemap syntax, we will
change the
version number of the sitemap namespace.
Is it really necessary to change the xml namespace? How does this help
developers?
If it's just a matter of being able to identify the version
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning
in the TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A long time
ago, we agreed that if we change
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning in the
TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning in the
TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for
Sylvain Wallez wrote:
Well, it would have been easy for us to allow it, simply by
defining builtin default values for map:pipes. I can't
remember of any other needed modifications.
We removed/deprecated a redirect to resources I think as well.
SNIP
Okay. So we should decide on how
Carsten Ziegeler wrote:
Ok. So I'll continue that way, which means removing your configuration merging stuff in favor of separate config files. Note that the size of these files has been largely reduced since they no more contain role definitions.
Go ahead.
Done!
The TreeBuilder is now a
