[Building Sakai] Fwd: ClassNotfound in a tool

[Anthony Whyte]

Scratch the suggestion below, I was think discussion not blogger.

Sorry,

Anth

Begin forwarded message:

> From: Anthony Whyte <arwhyte at umich.edu>
> Date: April 15, 2011 4:46:48 PM EDT
> To: daniel.merino at unavarra.es
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Subject: Re: [Building Sakai] ClassNotfound in a tool
> 
> Have you considered migrating your discussion content to msgcntr:
> 
> https://source.sakaiproject.org/contrib/ufp/discussion2forums/trunk/README.TXT
> 
> Review this page carefully to ensure that the migration can actually still be performed.
> 
> Cheers,
> 
> Anth
> 
> 
> On Apr 15, 2011, at 12:53 PM, daniel.merino at unavarra.es wrote:
> 
>> When we started with Sakai 2.5 three years ago, there were two blogger
>> versions, the 2.5 version and the post-2.5.
>> 
>> Post-2.5 was based on Wicket and had better display and functionalities,
>> so we chose it. Later, when official Blogger went out of the core tools,
>> we though that we had taken the right choice. But it seems that nobody
>> took it with us.
>> 
>> Today we "survive" with post 2.5 because Blogger still remains deprecated
>> and even if it was updated, there would not be DB migration scripts to
>> return to it. And Clog, which in fact is based in the post 2.5 work, seems
>> to be the future official tool but is not still widely used in production.
>> 
>> Another good point is if it will be easy to migrate from Post 2.5 to Clog.
>> It seems that all the migration efforts are pointed to the Blogger tool
>> and telling our users that they must start from scratch and lose their
>> previous posts is not going to be well received by them, I fear.
>> 
>> And, answering the other question, after deploying it, in
>> components/WEB-INF/lib there is only one jar: blog-tool-SNAPSHOT.jar . I
>> don't have access to my test server now, is a name similar to this.
>> 
>> Regards.
>> 
>> El Vie, 15 de Abril de 2011, 16:14, Seth Theriault escribió:
>>> Daniel Merino wrote:
>>> 
>>>> When deploying the blog post 2.5 tool, Maven doesn't copy
>>>> sakai-kernel-util.jar to that folder, and this is why we have
>>>> got this error.
>>>> 
>>>> Now I'm searching how to make Maven automatically copy the jar
>>>> in the deploy. The dependency is in the pom.xml, but it depends
>>>> of a profile. I don't know too much about Maven, but I'll keep
>>>> doing tests to fix the issue. Any idea?
>>> 
>>> Is there a particular reason why you are using the "post 2.5"
>>> version of this tool (I assume you are referring to the post_2-5
>>> branch)?
>>> 
>>> I think the easiest thing to do is to use a newer version fo this
>>> tool with your 2.7 deployment. Newer versions such as the 2.6 and
>>> 2.7 branches depend on the kernel by default.
>>> 
>>> Seth
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> 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/20110415/fea3e3f9/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110415/fea3e3f9/attachment.bin