[Building Sakai] CLOG for 2.8

[Omer A Piperdi]

Tool installed just fine.. When I 'Create new post'.. I get

INFO: EntityEncodingManager: No entities to format (json) and output for ref (/clog-post)
2011-07-20 11:44:59,461 ERROR http-8443-Processor14 org.sakaiproject.clog.tool.entityprovider.ClogPostEntityProvider - Caught exception whilst getting posts.java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
         at oracle.jdbc.driv

I don't see any table starting with 'CLOG' in database.. I am on Oracle 
10.2.4 by the way..

Thanks
Omer



On 7/20/2011 5:51 PM, Steve Swinsburg wrote:
> Hi Omer,
>
> What to the logs say?
>
> Cheers,
> Steve
>
>
> Sent from my iPad
>
> On 21/07/2011, at 3:10, Omer Piperdi<omer at rice.edu>  wrote:
>
>> Hi,
>>
>> I have deployed the CLOG trunk
>>     https://source.sakaiproject.org/contrib/clog/trunk/
>> with our 2.8 install..
>>
>> Even though I have auto.ddl=true in sakai.properties.. I don't see any CLOG tables created in the database.. Did I miss any setting or I need to run something sql manually?
>>
>>
>> Thanks
>> Omer
>>
>> On 7/18/2011 7:11 PM, Steve Swinsburg wrote:
>>> And if you want to manage your own binary deployer pom (like we do for additional tools), you can use a profile that is always active.
>>>
>>> Then you can just add and remove blocks for each tool you want to drop in:
>>> https://source.sakaiproject.org/svn//msub/anu.edu.au/alliance/2.8.x/extra-deploy/binary-overlays/pom.xml
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>>
>>>
>>> On 19/07/2011, at 12:48 AM, Anthony Whyte wrote:
>>>
>>>> Modify the core-deploy pom.xml as follows:
>>>>
>>>> 1. choose<profile>   <id>   = full
>>>>
>>>> 2.  Add a clean.target
>>>>
>>>> <properties>
>>>>                 <clean.targets>
>>>>                     components/accountvalidator-pack;
>>>>                     . . .
>>>>                     components/clog-pack;
>>>>             . . .
>>>>                     components/sitestats-component
>>>>                 </clean.targets>
>>>>                 <deploy.target>tomcat-overlay</deploy.target>
>>>>             </properties>
>>>>
>>>> 3. Add to<dependencies>
>>>>
>>>> <dependency>
>>>>                     <groupId>org.sakaiproject.clog</groupId>
>>>>                     <artifactId>clog-assembly</artifactId>
>>>>                     <version>0.9.1-SNAPSHOT</version>
>>>>                     <classifier>tomcat-overlay</classifier>
>>>>                     <type>zip</type>
>>>>                 </dependency>
>>>>
>>>> Note:  the above provides Clog trunk binaries, currently snapshot (e.g., unstable by definition) for your build.  The Clog trunk version is itself dependent on snapshot artifacts, including kernel-1.3.0-SNAPSHOT.
>>>>
>>>> Cheers,
>>>>
>>>> Anth
>>>>
>>>>
>>>> On Jul 18, 2011, at 10:24 AM, Jez Cope wrote:
>>>>
>>>>> Aha, Clog binary sounds useful - I use quilt to maintain local
>>>>> modifications against the codebase and it would be great to fold in clog
>>>>> as just another patch to the pom.
>>>>>
>>>>> I'm not very familiar with Maven - what's the correct syntax to add clog
>>>>> to the core-deploy project?
>>>>>
>>>>> Thanks,
>>>>> Jez
>>>>>
>>>>> Steve Swinsburg wrote:
>>>>>> Hi Omer,
>>>>>>
>>>>>> Use trunk for now. We've recently committed a number of fixes to trunk because 0.9 was unusable for us. That said there should be another tag coming soon. Also, clog is available as a binary so you can just add a pom block to the core-deploy project.
>>>>>>
>>>>>> Cheers
>>>>>> Steve
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On 15/07/2011, at 2:49, Omer Piperdi<omer at rice.edu>    wrote:
>>>>>>
>>>>>>> I am wondering if I should use 0.9 tag or trunk for CLOG with our Sakai 2.8.
>>>>>>>
>>>>>>> Thanks for any suggestion.
>>>>>>>
>>>>>>> Omer
>>>>>>> _______________________________________________
>>>>>>> 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"
>>> _______________________________________________
>>> 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"
>>>
>>>
>>>
>>>
> !DSPAM:2294,4e275bc2144542335084035!
>
>