[Building Sakai] Sakai tool installer

[Steven Githens]

+1

Some sort of text file or small embedded database to track this would be 
great.

It would be nice to add some of this to the sakai:deploy/sakai:undeploy 
maven plugin (we could even look at using the groovy or jruby maven2 
support to get it done nicely).

The sakai:(un)deploy plugin could also read this database.  And it could 
warn you if you're trying to build and install something that has a 
conflicting version in components or shared/lib already, and ask you to 
unistall them first, etc etc.

In addition to Matt's big list this sounds like an awesome BOF.  ( it 
would also be cool to explore making debian or rpm packages etc for Sakai ).

-Steve


David Haines wrote:
> Is anyone interested in a BOF at the conference on building a Sakai 
> tool "installer"?  This functionality has been suggested for years but 
> never has happened.  We should figure out if it is easy and then do 
> it, or figure out how to make it easy.
>
> The basic hope is that someone could, at worse, create a text file 
> that lists appropriate tools and the installer would assemble a Sakai 
> image that could be deployed into Tomcat.  An imaginary example is below:
>
> Sakai-base-2.7.3
> blogwow-1.2.3
> disabler-tool-0.5
> autojoin-umich-0.1
>
> Even with a UI as boring as a text editor this would make creating a 
> Sakai installation easier.
>
> - Dave
>
> David Haines
> CTools Developer
> Digital Media Commons
> University of Michigan 
> dlhaines at umich.edu <mailto:dlhaines at umich.edu>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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"