On Tue, Nov 17, 2009 at 3:20 PM, Simon Laws <[email protected]> wrote:
> - my 2.x build (without otests) is already up to 45 minutes and there > are still more extensions to bring back in > It takes similar or even longer on my old machine, and thats with the local repo already populated. Doing a fresh checkout and build with an empty or out-of-date local repository can take hours. Thats too long and i think one of the reasons we find it so hard to attracted new committers - if someone sets aside a few hours in an evening or weekend to play with Tuscany and they can't even get a build done in that time then its going to be difficult for them to contribute much. And thats not just newbies, I've heard recently from a few experienced but less active Tuscany people that they're afraid to do an svn up as they expect to then need to spend hours or even days getting their environment working again. > 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. > Giorgio tried something similar not so long ago with a Maven profile for just some core modules and based on that I've added a "base" profile and a "jms" profile - you can try those in the Tuscany top level folder doing mvn -Pbase or mvn -Pjms or mvn -Pbase,jms. I've also tried an alternative with svn externals so you can checkout and build just a subset of the modules needed to run the SCA-J CAA tests - https://svn.apache.org/repos/asf/tuscany/sandbox/scajcaa/ > In the first instance I'm interested in peoples comments on > the principle of a more structured build. > We've seen from 1.x and now 2.x that the current approach doesn't scale so I'm very much in favour of a more structured build. Those maven profiles I mentioned above have been interesting but they're not that usable, I'd like to rearrange the trunk structure with the core/base and extensions separated and with things like the the samples and tests for each extension all under its own subtree for the extension. ...ant
