As a wicket-stuff developer, I for one would hate to see restrictions
placed on what can or can not be a wicket-stuff project. The beauty
of the wicket-stuff idea is that it is a playground for people try out
potentially cool ideas. It's a place for people to learn how to use
wicket and build "possibly" cool widgets and tools.
I know that *my* project (wicketstuff-scriptaculous) has occasionally
been left "in the dark" for several months before a whole slew of
changes and features get built in.
Sure, there may be a "better" wicket/hibernate project out there (aka:
databinder), but I really don't see any issues with that. Especially
now that there's a wicket-stuff wiki, it can be clearly spelled out
there what each project's strengths/weaknesses are.
Yes, I completely agree with that. It's in fact what we've been
advertising wicket-stuff is about.
Anyway, I've deleted wicket-contrib-data,
wicket-contrib-data-hibernate3 and wicket-contrib-examples. I'm
working on moving the Velocity project to core. The license is
compatible, I've heard from various people using it, and in this way I
can move the example to the wicket-examples project.
Eelco
