Actually I agree with wendy here... a shared build and release should be mandatory, otherwise it will be versioning hell.
The parts i like to see in the commons are mainly Validators, Converters and other renderkid independent stuff with stable api. I see no reason to release tomahawk just to have a release of commons with some additional well tested converters included. Or to delay a commons release because of problems in tomahawk. I dont see a versioning hell here, tomahawk and the sugested commons should be independend. If there parts inside on which tomahawk relays, there is no problem tomahawk also relays on commons-collections and other libs without binding to there release cycles. And there should be nothing in which is a tomahawk specific item without use for other jsf librarys.
