[Deploying Sakai] [Building Sakai] Trunk: ui package proposal

[Steve Swinsburg]

> For example, people who have changes
> to "independent" packages must deploy into a Maven repository in
> some way and that's a new semi-required step. Ditto for a
> required "independent" package like the K1 Kernel.

If you have local customisations to code that is now in one of the  
packages (Common, Edu Services, et al) then you can simply check out  
the source and patch in the usual fashion. I agree its a bit more work  
and a number of sources have disappeared from a trunk checkout but for  
most users is making things easier.

Once patched however, you don't need to deploy these updated artifacts  
to a Maven repository (except your local one) for it to work. It's  
just like the Kernel - you can patch the source locally, build and be  
on your way with your updated Kernel artifacts. So there is no extra  
step for deployment.

If you need to share source (we've been using mSub to manage this) you  
could create a local shared Maven repository on a spare box in the  
corner pretty quickly and push your artifacts there for other local  
implementors to pull from.

regards,
Steve


On 11/11/2009, at 5:29 AM, Berg, A.M. wrote:

> Later when the "independent pieces settled"
>
> I like the http://eclipsesource.com/en/yoxos/ site for Eclipse where  
> you can blend a distribution out of Eclipses core and plugins. One  
> could imagine a GUI like tool doing something similar for Sakai  
> pom.xml and .externals, but then you would have to give clear  
> definition of the quality of each generated profile so the end user  
> could decide the relative risks and benefits.
>
> Alan
>
> Alan Berg
>
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
>
> http://home.uva.nl/a.m.berg
>
>
>
>
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org on behalf of Mark  
> Norton
> Sent: Tue 10-11-2009 17:41
> To: Seth Theriault
> Cc: production at collab.sakaiproject.org; Developers List
> Subject: Re: [Building Sakai] [Deploying Sakai]  Trunk: ui package  
> proposal
>
> Seth Theriault wrote:
> > Another observation is that the semi-rapid movement from a
> > monolithic release (2.5) to a separated release (2.6 + K1) to a
> > more modular bundle (2.7 + K1 + "independents") may be leaving
> > some people in the dust. That's my main thrust here.
> >
> There was talk at one point about creating identified monolithic  
> builds
> after most of the major tools in Sakai were made independent.   
> Having a
> simple way to build Sakai with Samigo automatically include (or  
> similar
> builds) is a desirable thing.  That said, I don't think we are at the
> point of creating these custom aggregate builds.  We need to get the
> independent pieces settled before they can be used (easily) to make
> larger structures.
>
> - Mark Norton
> _______________________________________________
> 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"
>
>
>
>
>
> _______________________________________________
> 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/production/attachments/20091111/78066754/attachment.html