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

[Aaron Zeckoski]

> 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