[Building Sakai] Updating component jars during development

[Adrian Fish]

It's a fair question, not daft at all, but I'm afraid the restarting tomcat
bit has to happen as that's when the components get loaded.

A good approach is just to strip stuff out of your Sakai that you're not
working on (the reasoning behind the cafe build) so it starts up quicker.
It's also a good idea to do most of your prototype development in a webapp
and refactor into services later, if at all. There's lots of stuff in
components that probably shouldn't actually be there as nothing except the
related tool ever calls it.

Cheers,
Adrian.

On 25 June 2012 14:31, Raad Al-Rawi <Raad.Al-Rawi at admin.cam.ac.uk> wrote:

> Hello All
>
> This may be (and probably is) a daft question, but here goes...
>
> If you change code which compiles to a component jar (like impl stuff), is
> there a better (quicker/easier) way of deploying it to your dev. instance
> than compiling it, stopping tomcat, copying the jar over, and restarting
> tomcat?
>
>
> Cheers!
>
> R
> ~~
> Raad Al-Rawi
> CamTools Operations Analyst
> University of Cambridge
>
> Management Information Services Division
> Greenwich House
> Madingley Rise
> Cambridge
> CB3 0TX
> UK
>
> Tel: +44 (0)1223 760905
>
>
> _______________________________________________
> 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/20120625/2d79d0fe/attachment.html