[Building Sakai] sakai-2.9.x-all build broken

[David Adams]

Matthew Jones wrote:
> Also for 2.9, Aaron did quite a bit of work to turn *most* of kernel-util
> into a service, so that if you modified kernel you don't have to re-build
> everything. There are still classes in kernel-util but they aren't
> implementations anymore so they should be changed MUCH less often (like
> never in a major release)

This is good to hear. I see there are also "kernel-storage-util" jars in some war files and components. Are those similarly just interfaces?

All that said, we do locally modify even the interfaces for certain needs. And so a build that includes all the source code is a requirement for us. When the kernel was broken out of Sakai several releases ago, that was annoying, but not super painful to reintegrate. However, as more and more subprojects are indie-fied it has become a major effort to recreate a full source code build locally with each release. Perhaps getting rid of purepoms will make that process a little easier for us this time around.

In any case, feedback on this list seems to indicate that at least a few schools do have a need for full source availability. I wonder how many schools are actually productively using a source distribution in which literally half of the subprojects have been stripped out (sakai-2.9.x-all has 68 externals, sakai-2.9.x has 34).

I hope that some other schools will jump in with their opinions on this. If I'm the only one bugged by this trend in the "source" distribution, then I'll accept my role as a jabbering crank and go back to work. :)

-dave
-- 
David Adams
Director, Learning Systems Integration and Support
Virginia Tech Learning Technologies