[Building Sakai] : Re: sakai-2.9.x-all build broken

[Matthew Jones]

Hi Mustansar,

I keep track of this information on confluence, generally all on one page.
Previously this was something Maven figured out automatically.

https://confluence.sakaiproject.org/display/REL/Indie+release+order+-+2.9

Keeping it in multiple places might have a better chance of it being out of
date, and since generally I'm the only one doing it (on limited time) I'm
not going to spend time updating all of these other places. If you think
there's a better idea and/or want to contribute time work on something like
this let me or the cle-release-team at collab.sakaiproject.org know!


On Sat, Nov 17, 2012 at 5:01 PM, Mustansar Mehmood <mustansar at rice.edu>wrote:

>
> I forgot to cc the mailing list, apologies.
> ./mustansar
>
> -------- Original Message --------  Subject: Re: [Building Sakai]
> sakai-2.9.x-all build broken  Date: Sat, 17 Nov 2012 15:56:18 -0600  From:
> Mustansar Mehmood <mustansar at rice.edu> <mustansar at rice.edu>  To: Steve
> Swinsburg <steve.swinsburg at gmail.com> <steve.swinsburg at gmail.com>
>
> +1
> I think tools needs to have some information in pom.xml or a README to
> indicate regarding what a particular "tool"(I am not talking about jar
> dependencies here) depends on, in terms of other tools. Clearer
> distinction will give deployment institution more freedom of choice in
> terms to tools to deploy as well tool developer(s) get to be more aware
> of what other tool developers they have to collaborate to keep their
> tools functional.
> ./mustansar
>  O11/16/2012 10:10 PM, Steve Swinsburg wrote:
> > On 17/11/2012, at 11:05 AM, Seth Theriault <slt at columbia.edu> <slt at columbia.edu> wrote:
> >>
> >> On the subject of indie-fication, my personal opinion is that it's a
> >> bit out of control and needs to be scaled back. Feel free to call this
> >> re-evaluation if you like. It was said to greatly simplify release and
> >> deployment, but I don't think it has seen the level of expected
> >> benefits. If you look at the evolution from 2.6 (kernel is the only
> >> indie) to 2.7 (couple of indies) to 2.8 (more indies), it got harder
> >> and hard to keep track of what is actively being developed and what
> >> was just being indie-fied for other reasons.
> >
> > Totally agree here. For example the portal is an indie, though its kind of a required component... IMO there should be a core set of components that allow Sakai to build and run. Kind of like what the cafe build use to be, the minimum. That should be the default source code. Then the rest of the tools are available as indies and then it becomes like a plugin based approach. Those that want to build everything from source still can by modifying the externals/msub.
> >
> > cheers,
> > Steve
> >
> > _______________________________________________
> > 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/sakai-dev/attachments/20121119/0aaecc76/attachment.html