Ok, options A and B both would be over design. So... Option C: > C. Stopping support of wicketstuff-push and just having that inside > wicketstuff-dojo.... (Obviously my least favorite option, I wouldn't have > even considered it, if you hadn't forced my hand...)
Its basically just project dependencies, but, KISS is a good enough reason to disband wicketstuff-push... I think the way to do it is: After you get wicketstuff-dojo stable and checked int, mark some classes in wicketstuff-push as deprecated and point them to the dojo project... Maybe if sometime soon we integrate push into wicket's core (as per another thread running around), then it doesn't matter what we decide...
