Need to have a multi-module maven project structure something like this:
rome-certiorem (pom) - top level module
rome-certiorem-core (jar) - core module with stuff needed by multiple modules
rome-certiorem-hub (jar) - module providing hub support
rome-certiorem-sub (jar) - module providing sub support
rome-certiorem-pub (jar) - module providing pub support
Hmm... So I am kind of thinking...
I am not opposed to this at all, but it seems like it would be a lot of jars, and I am not sure there is enough code right now where "core" would be more than a handful of classes. since hub and sub both, basically, have to exist inside a fully-loaded environment (with most of ROME and some kind of web container), it might make more sense to have a jar that contains pub and common (client), and one that contains hub and sub that depends on the client.
It might also make sense to keep everything in one jar with all the deps declared as optional, and just publish profile POMs that contain limited transitive dependencies.
@Robert: Very good points. I will hold off this issue and make it a low priority with no target release. We can revisit it later as we gain more deployment experience.