I'm +1 for this. I haven't looked at the package structure, but I can imagine moving some stuff around as well. Perhaps someone with a vision (pun intended) could make a proposal?

I *do* think we should do this as soon as possible as the API freeze is coming quickly!

Martijn

Jonathan Locke wrote:

i can't recall what lame-o argument i had for keeping the voicetribe package name, but it would make a lot more sense to me now to call the wicket package simply "wicket.*" this isn't likely to cause a conflict
and if the project ever moved it wouldn't need to be changed. +1/-1 anyone?





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to