> What's the point of making you jump through hoops to enable this?
> - It'll require thought to not break reusable components, as Igor says. That's the responsibility of individual projects. People can create custom tags and stuff as well. > - It's extra config- and API-width we don't need; we'll have to > deprecate the method to turn it on once it becomes "standard", > mention it in migration docs for 1.5(?), support it on the mailing > list, etc. etc. > > - If we add it, it looks like lots of people will use it. We're then > stuck with it - it's a change that would never get backed out unless > someone comes up with a vastly better way of doing all this such that > it's completely obsolete. What I would be ready to do is ensure that people who want this can implement it. We could ship it with Wicket (but disabled), or just leave it outside altogether, leaving it up to users to create e.g. a wicket-stuff project for it. I agree we shouldn't make it our responsibility, not even a little bit, and certainly shouldn't hint that this would be the way to go when a couple of core developers don't agree with it in the first place. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
