[Building Sakai] Customizing Sakai: Excluding Modules

[Steve Swinsburg]

Hi Axel,

Yes, if you do not want them in your build you can just remove them from the pom so they are not built. However some modules depend on each other so sometimes you need to keep one deployed to satisfy the other. Generally this is just the API though so you can comment out certain sections of each modules pom to stop the tool from deploying, but keep the API, for example.

You can see a very stripped back version here:
https://source.sakaiproject.org/svn//msub/anu.edu.au/services/2.8.x/

Also, some are deployed as binary so check the core-deploy pom also, and comment out the sections you dont need.

You could later remove them from the source completely so the code is a bit smaller.

cheers,
Steve



On 10/09/2012, at 12:23 PM, Axel Theorin <axel.theorin at gmail.com> wrote:

> Hi!
> 
> I'm using Sakai 2.9 as a platform for building a communication,
> collaboration, and data-sharing portal for students and researchers.
> While the portal is intended for use primary by academics, it is not
> tied to any particular institution, nor while it be used to organize
> any teaching activities. Therefore, modules/functionality like
> gradebook and assignment etc. don't make any sense for me and I would
> like to exclude them from my installation (and if possible from my
> repository).
> 
> Can I do this by just removing references to the unnecessary modules
> from the top-level pom.xml?
> 
> Any hints on how I should proceed in pruning the source-tree would be
> much appreciated.
> 
> Thank you in advance!
> 
> Best regards,
> 
> Axel Theorin
> Tokyo University of Foreign Studies
> _______________________________________________
> 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"