[Building Sakai] Apply SAM-756 to 2.7.1 - Where is samigo!?

[Steve Swinsburg]

What I meant was that if you do nothing, your build will use the pre built and tagged release of Samigo and it will be installed automatically into Tomcat. You can check the version in the master pom. Because of this, the source has been removed from the Sakai checkouts because it is not required. 

If you need to make any modifications, you need to grab the source.

Cheers
Steve


Sent from my iPhone

On 07/10/2010, at 16:11, Lydia Li <lydial at stanford.edu> wrote:

> Hi Warwick,
> 
> I'm not sure what Steve meant by 'just grabbing the source' vs. 'using the indie release'.   Maybe he was talking about checking out the indie project source under Sakai, vs. at the same level as Sakai?  Either way would work.  Hopefully Steve will reply to your email soon. 
> 
> I've not tried the steps described in Nicola's link, or David's blog myself, but our method (we make local changes for kernel, samigo and msgcntr indie projects at our institution.)  is just another variation.   There are different ways to modify an indie project, depending on where you check out your indie source, or how you maintain your version, but the theory is the same once you understand how mvn deploys artifacts into your tomcat.   
> 
> thanks,
> Lydia
> 
> 
> On 10/6/10 3:22 PM, Warwick Chapman wrote:
>> 
>> Yep Lydia, I saw that, read that and the link at the bottom to David's blog.  What is not obvious to me is how to do this without the mvn -o local stuff which I'm not familiar with.  It's late, I'm hoping to get a build out which corrects this issue for a test tomorrow and battling a little with the overall complexity here.
>> 
>> Steve has suggested in an email after this one that just grabbing the source and using that will work instead of using the indie release.  Is Sam's pom.xml edit implied in Steve's response below or not required?
>> 
>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>> 
>> 
>> On Wed, Oct 6, 2010 at 11:35 PM, Lydia Li <lydial at stanford.edu> wrote:
>> You don't have to go the artifact route.   Matthew's earlier email:
>> 
>> 
>> "Here was a doc that Nicola wrote about customizing an indie release.
>> http://confluence.sakaiproject.org/display/SAKDEV/Customizing+'indie'+releases
>> "
>> 
>> includes a link to a doc about customizing an indie release,  which is exactly what you wanted : download the src, patch, build and deploy. 
>> 
>> 
>> 
>> thanks,
>> Lydia
>> 
>> 
>> 
>> On 10/6/10 1:03 PM, Warwick Chapman wrote:
>>> 
>>> Do I have to go the artifact route?  Can I not just download the src, patch, build and deploy?
>>> 
>>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>> 
>>> 
>>> On Wed, Oct 6, 2010 at 9:36 PM, Matthew Jones <jonespm at umich.edu> wrote:
>>> As an independent release it doesn't get built, it just gets downloaded and deployed as part of the core-deploy project:
>>> https://source.sakaiproject.org/svn/sakai/trunk/core-deploy/
>>> 
>>> Here was a doc that Nicola wrote about customizing an indie release.
>>> http://confluence.sakaiproject.org/display/SAKDEV/Customizing+'indie'+releases
>>> 
>>> -Matthew
>>> 
>>> 
>>> On Wed, Oct 6, 2010 at 3:25 PM, Warwick Chapman <warwickchapman at gmail.com> wrote:
>>> Thanks Sam.  How did it get built without me fetching that samigo sources myself?
>>> 
>>> 
>>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>> 
>>> 
>>> On Wed, Oct 6, 2010 at 9:23 PM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
>>> Samigo is now an independent release project.  You need to check out a branch of the project and build manually.
>>> 
>>> Along with SAM-756, I recommend SAM-801 (Allow student use of rich-text editor).
>>> 
>>> Here is the 2.7.x branch:
>>> 
>>>   https://source.sakaiproject.org/svn/sam/branches/samigo-2.7.x/
>>> 
>>> Make sure to clear all previous Samigo artifacts before deploying (webapps/samigo*, components/samigo*, shared/lib/samigo-*).
>>> 
>>> --Sam
>>> 
>>> 
>>> 
>>> On 10/6/2010 3:16 PM, Warwick Chapman wrote:
>>>> Hi All
>>>> 
>>>> I want to apply http://jira.sakaiproject.org/browse/SAM-756 to Samigo so my MySQL-backed Sakai instance can take input of more than 4000 characters.  I cannot find samigo in my source tree!  Am I missing something?
>>>> 
>>>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>>> 
>>>> _______________________________________________
>>>> 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"
>>> 
>>> 
>>> _______________________________________________
>>> 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/20101007/dc18651a/attachment.html