On Mon, Jan 20, 2014 at 10:59 AM, Martin Grigorov <[email protected]> wrote: > Yes, evaluating which experimental modules to become stable is an entry in > the roadmap document but I intentionally left it out of this discussion > because I think it deserves more discussions. But since you started ...
> wicket-cdi-1.1 is very new. I guess no one uses it so far. > Did Topicus migrated to 6.13 yet ? > Igor did your product move to wicket-cdi-1.1 ? > But since wicket-cdi-1.1 has evolved from wicket-cdi(-1.0) I believe it is > mature enough to be part of the stable module in Wicket 7. We have CDI-1.1 in our current project. It has yet to reach anything near a testing environment, but for development it seems to work. > Wicket Bean Validation (JSR303) seems to be working fine. There were just a > few issues with it. I'm +1 to make it stable module. > > Wicket Native WebSockets: > I personally like it and I'd like to make it even better based on users' > feedback. > We use it in an internal project. > My only concern about making it stable is that it will be harder to make > improvements(API breaks) when more people start to use it. > I am +1 to make it stable. You can make it stable in 6.x, and break API until we release 7.0 ;-) > Wicket-Bootstrap: I think this module should be removed. Yup. Though we should add a webjars resource reference into wicket-extensions that enables easy inclusion of any webjar framework. > Wicket Examples NG can use Michael Haitz's > Wicket-Bootstrap<https://github.com/l0rdn1kk0n/wicket-bootstrap> or > move the code from the experimental Wicket-Bootstrap to its packages. I'd suggest remove Wicket Examples NG for now (move to a branch or so). I can't see that any time is going into that project for now, and any time invested should rather go into the user guide and fixing 7.0 issues. I'm not *that* heavily attached to these two projects. Martijn
