[Building Sakai] Problem with 2.9.1

[Matthew Jones]

Well, either you deployed 2.9.1 over on top of 2.9.0 and have duplicate
jars somewhere in components or you got the wrong versions from somewhere.
There really isn't any way easily to tell as java classes don't have any
version marks, only the .jar files do. I'd go into the components directory
and run

find . -name "sakai*-kernel*.jar"

And see what versions come up on the jar files, ideally nothing with 2.9.0
is in that list. You can also list what jars the running process has loaded.

lsof -p <process id of java process running tomcat> | awk {'print $9'} |
sort | grep kernel

Would also list all of the kernel jars that were loaded. I don't know of
any other way to tell what's going on though. That version on the bottom is
only based on a property generated during the build so makes no guarantees
if you compiled yourself (rather than running the provided demo/binary)


On Mon, Feb 18, 2013 at 4:44 PM, Javier Martinez <javier at fisica.unam.mx>wrote:

> Hi,
>
> I didn´t override any of these variables.
>
> I overrided it with 2.9.1 and now  I can see the correct version in the
> portal. But, How can I know if I'm working with the new kernel and version?
>
>
>
>
>  Javier Martinez
> javier at fisica.unam.mx
>
>
>
> On 18 Feb, 2013, at 1:25 PM, Matthew Jones wrote:
>
> e overriding *version.service*, *version.sakai* and *version.kernel* propertiesin
> a local sakai.properties in your sakai directory in the tomcat, it will
> still reflect whatever versions are there.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130218/37f1f409/attachment.html