[Building Sakai] Abundance of pom.xml files in 2.9

Steve Swinsburg steve.swinsburg at gmail.com
Tue Jul 23 01:27:15 PDT 2013


Hi Mike

You are probably best taking the relevant -all branch or tag and forgetting about the binary indies, which are what the deploy poms do. Then the source layout is the same as what you are used to. Note that some services are now in edu-services and in common. 

Cheers
Steve

Sent from my iPhone

On 23/07/2013, at 13:00, Michael Osterman <ostermmg.sakai at gmail.com> wrote:

> Hello,
> 
> We're doing a pretty big jump from 2.6 to 2.9 this summer, and are having some issues with our 2.9 build from source, likely because we missed a lot in the intervening years. :/ Specifically, we seem to be missing the CourseManagementAPI, which seems like it may be provided by framework-shared-deploy/pom.xml. Will test that theory in the a.m.
> 
> That specific bit aside, we're wanting to better understand the new source layout and best practices for building a custom Sakai 2.9 from source.
> 
> In 2.6, we had the following before doing an svn pull and build:
> .externals
> pom.xml
> kernel-deploy/
> 
> All of these were tuned to enable only the modules/tools we wanted
> 
> Now, it looks like there are a handful of new directories in addition to what we were accustomed in 2.6, according to https://source.sakaiproject.org/svn/sakai/branches/sakai-2.9.x/:
> core-deploy/
> framework-shared-deploy/
> jstl-shared-deploy/
> 
> Looking at the Vula 2.9.x build, it looks like one wants to include those 3 new directories and customize the core-deploy directory to enable/disable:
> http://source.cet.uct.ac.za/svn/sakai/vula/branches/vula-2.9.x/.externals
> 
> Does anyone know where to find any documentation on customizing ones own build via the pom.xml files for 2.9? I can't seem to find anything written down anywhere.
> 
> Barring that, as such documentation may not exist, can someone provide a thumbnail sketch of best practices for building from source in 2.9 with regard to modifying the root pom.xml and those within the now four sub-directories?
> 
> Cheers!
> Mike
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130723/f76a227c/attachment.html 


More information about the sakai-dev mailing list