I raise this topic with some trepidation as we've been here before but here goes. We have been building (and releasing) all of the code in the 2.x code base which has worked well to date. However two things make me pause for thought:
- we are not running the otests as part of the main build and we are already seeing regressions because of this (this will happen more often as more otests are brought in). This is not good. - my 2.x build (without otests) is already up to 45 minutes and there are still more extensions to bring back in Now, there may some tuning I can do on my machine to improve build performance but I would like to experiment with building the core modules, along with a core set of extensions and associated otests independently of other extensions. Of course there is nothing stopping me doing this experiment locally (and I will) but there are wider implications for this that I would like us to discuss in parallel. My primary concern being that we can produce and test a well defined extension SPI (which I don't think we are very good at) and also separate those modules which we think are becoming stable from those that are not ready yet. I have avoided using words like features, shades, distributions etc here on purpose. These may all be part of the answer. I've also not touched on the release structure as I would like to keep that separate. In the first instance I'm interested in peoples comments on the principle of a more structured build. Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
