[sakai-pmc] [Building Sakai] RSS portlet now part of Sakai trunk

Tue Feb 25 06:41:36 PST 2014

Interesting, I didn't know github did this. [1] Still doesn't explain why
nightly trunk regular failed the 8AM, unable to find rss. If I 'svn co'
that path it looks like it does work as you describe.

[ERROR]   The project org.sakaiproject:base:11-SNAPSHOT
(/home/tomcat-nightly/sakai/pom.xml) has 1 error
[ERROR]     Child module /home/tomcat-nightly/sakai/rss of
/home/tomcat-nightly/sakai/pom.xml does not exist

http://nightly2.sakaiproject.org/logs/sakai-nightly/build-2014-02-25-08:00:01.log.txt

Though those other directories like clog and yaft give 404 errors.
https://github.com/adrianfish/clog/trunk

Experimental has been down for a week, ever since the 11 cut. I spent a
little time on it but haven't got it back up again.

[1] https://github.com/blog/1178-collaborating-on-github-with-subversion

On Tue, Feb 25, 2014 at 9:32 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> >> You can't add a github module to an SVN externals, it only works for
> SVN repos.
>
> Not true.  I cleaned up projects associated with the experimental build a
> couple of weeks ago and included three github-based contrib projects in the
> checkout: clog, clogdashboardintegration and yaft. [1]   Between 11-17
> February the experimental build checked out and built all three contrib
> projects originating from github without incident (see the logs). [2]
> However, since 18 February the experimental build has for unknown reasons
> reverted a non-experimental profile.  I'll check with Greg Thomas of IU as
> to the reasons for this misbehavior.
>
> That said, the purpose of the experimental branch is rather different than
> trunk.  It's a convenience branch serving a nightly instance that provides
> a sampling of non-core Sakai capabilities for review purposes.  It's not a
> development branch.  It's nightly eye candy.
>
> I concur with the view that SVN remains the authoritative source repo and
> that the rss code destined to trunk needs to live in the SVN core repo
> until we make the switch to Github.
>
> Cheers,
>
> Anth
>
>
> [1]
> https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-experimental/.externals
>
> . . .
>
> # Experimental (contrib)
> assignment2 https://source.sakaiproject.org/contrib/assignment2/trunk
> dashboard https://source.sakaiproject.org/contrib/dashboard/trunk
> endorsed https://source.sakaiproject.org/contrib/endorsed/trunk
> evaluation https://source.sakaiproject.org/contrib/evaluation/trunk
> formbuilder https://source.sakaiproject.org/contrib/ucf/formbuilder/trunk
> reports https://source.sakaiproject.org/svn/reports/trunk
>
> # Experimental (Github)
> clog https://github.com/adrianfish/clog/trunk
> clogdashboardintegration
> https://github.com/adrianfish/clogdashboardintegration/trunk
> yaft https://github.com/adrianfish/yaft/trunk
>
> [2] example:
> http://nightly2.sakaiproject.org/logs/build-contrib/build-2014-02-17-02:30:01.log.txt
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
> On Feb 25, 2014, at 8:51 AM, Aaron Zeckoski wrote:
>
> >> In the end we'll probably have to do something to clone this in SVN or
> the
> >> entire source build process seems like it would need to change. Even if
> >> there's a way for maven to clone this repo, I still don't know if it
> would
> >> be able to work. Locally we have a shell script to do it, but then
> everyone
> >> would need to run that (and have git installed) in order to build Sakai.
> >
> > That seems like a non-starter until we get things moved over to git.
> > -AZ
> >
> >
> > On Tue, Feb 25, 2014 at 8:45 AM, Matthew Jones <matthew at longsight.com>
> wrote:
> >> Also, currently nightly is down as of 8AM. You can't add a github
> module to
> >> an SVN externals, it only works for SVN repos. We'd have to have a
> special 2
> >> pass parser for the externals file in order to handle something like
> that,
> >> which we don't have now on nightly, it's just an svn. So we'll need to
> >> revert this until we work out how to either checkout the git module
> separate
> >> from these or put the rss into svn.
> >>
> >> In the end we'll probably have to do something to clone this in SVN or
> the
> >> entire source build process seems like it would need to change. Even if
> >> there's a way for maven to clone this repo, I still don't know if it
> would
> >> be able to work. Locally we have a shell script to do it, but then
> everyone
> >> would need to run that (and have git installed) in order to build Sakai.
> >>
> >>
> >> On Tue, Feb 25, 2014 at 8:35 AM, Steve Swinsburg <
> steve.swinsburg at gmail.com>
> >> wrote:
> >>>
> >>> Old habit when they used to be open by default - Jira updated. I
> replied
> >>> to the code location question in the Jira.
> >>>
> >>> cheers,
> >>> S
> >>>
> >>>
> >>> On Wed, Feb 26, 2014 at 12:09 AM, Aaron Zeckoski <azeckoski at unicon.net
> >
> >>> wrote:
> >>>>
> >>>> Is https://jira.sakaiproject.org/browse/SAK-25784 the right ticket?
> If
> >>>> so, why is the ticket in the awaiting review and unassigned state when
> >>>> it appears all the work was already done and committed? Did anyone
> >>>> review this before commit?
> >>>>
> >>>> On the github thing, do we actually want core code split between the
> >>>> main svn repo and some other repo (whatever it is not being the point
> >>>> of the question)? This is probably a discussion for another thread but
> >>>> I think maybe we want all core code in the repo (as opposed to contrib
> >>>> code that could be anywhere really).
> >>>>
> >>>> Other comments in the ticket.
> >>>> -AZ
> >>>>
> >>>>
> >>>> On Tue, Feb 25, 2014 at 8:00 AM, Steve Swinsburg
> >>>> <steve.swinsburg at gmail.com> wrote:
> >>>>> Hello,
> >>>>>
> >>>>> The Simple RSS Portlet has now been integrated into trunk, see:
> >>>>> https://jira.sakaiproject.org/browse/SAK-25784
> >>>>>
> >>>>> This is a JSR-168 portlet rather than a Sakai tool and detailed
> >>>>> information
> >>>>> can be found here:
> >>>>> https://wiki.jasig.org/display/PLT/Simple+RSS+Portlet
> >>>>>
> >>>>> Included in the recent commits is conversion SQL to replace all
> >>>>> instances of
> >>>>> the current News tool and copy across the URLs and settings.
> >>>>>
> >>>>> This replacement was due to be part of Sakai 10 but just missed the
> >>>>> branch
> >>>>> date. It is currently in trunk only.
> >>>>>
> >>>>> Of note, this code actually lives in github and the Sakai 10
> compatible
> >>>>> branch is pulled in via the standard SVN externals. The way of the
> >>>>> future
> >>>>> maybe :)
> >>>>>
> >>>>> All feedback appreciated.
> >>>>>
> >>>>> regards,
> >>>>> 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"
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> sakai-pmc mailing list
> >>> sakai-pmc at collab.sakaiproject.org
> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> >>>
> >>
> >
> >
> >
> > --
> > Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> > _______________________________________________
> > sakai-pmc mailing list
> > sakai-pmc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140225/885279dd/attachment-0001.html 