Hi, In my view, "modularization" is not equal to "creating many Maven projects".
>- Bundles that do one and only one thing are more cohesive in their >implementation. Currently, oak-core does too many things and exposes a >low degree of cohesion. OK, this is your opinion, but I don't agree. I don't think that oak-core does too many things. In fact, I think we would be better of if oak is just one bundle. >- Providing and distributing a focused, small fix for a component is >easier if that component is contained in its own bundle, because it >prevents the release of oak-core in its entirety. That would require we completely change the way we work in Oak. We don't release each module separately, and we don't test combinations of versions. And I think that's OK, because doing that would lower the quality and increase our work, without real benefit for anybody. >- Semantic versioning will not be of a big help, because the release >notes already give a good overview of the impact of every release. I'm not sure how said that. I think semantic versioning is OK. Regards, Thomas
