Hi all, and sorry for the late reply, I've been travelling outside Italy and didn't have an Internet connection!
> Currently I only think on the users. > In future (I mean after > graduation) we will be our own reviewers and well, we have to deal > with our own things then. I would like to build packages which make > technical sense, not ones which is easy to vote on (if both can be > achieved, good). > *best*quote*ever*, couldn't agree more! > Actually we should think in this case if it makes sense to make jar > files for a single class. Or if we should just provide a single jar. what about supporting both? I mean, nothing prevents having small micro-modules AND a big fat-package. Some other Onami modules could be affected by the same "issue", like SPI, where we can identify a core module, which provide the SPI discovery engine, the Services discovery module and the Guice Module loader: actually the source are all merged in a single module, but nothing prevents us distributing them as mini-modules AND the fat jar. Let me do an experiment on the sandbox as soon as I have some spare time in order to prove that this is something we can achieve, then we'll evaluate. Thanks all a lot for the feedbacks! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/
