On Mon, Jul 7, 2008 at 11:38 AM, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> No particular reason other then that we are trying to make the > migration from wicket 1.3 to wicket 1.4 as small as possible. > There has not been an official vote on this yet but the plan is to > integrate it in wicket 1.5 which we will begin working on shortly > after 1.4 has been released. I'm not trying to flame here or anything, but from what I've read of Swarm/Wasp, it's quite complicated and that would go against the spirit of Wicket, IMHO. Also, it uses external files for configuration. Again, this goes against the spirit of Wicket. Perhaps if there were a programmatic way of configuring everything? Again, I've never used it, but I've seen responses on the lists about how to do things and it just scared me away from it. That's just my $0.02. To be fair, maybe I should play with it a bit to see it for myself, but I haven't had the cycles. Sorry.
