I haven't found any issues with it. I did upgrade it when I was working on getting the full blown clustering to work with jackrabbit internal cache.


When that didn't work out and we stuck with the HA-Singleton approach, we scrapped the plans to upgrade it in 2.4.

But looking at their Release notes, it wont break our CMS and it didn't when I used it

According to the release notes:
http://apache.mirrors.tds.net/jackrabbit/RELEASE-NOTES.txt
there are a number of bug fixes including fixes for memory leaks, concurrency issues, problems with versioning, etc.

And as Sohil indicated, it should be a drop-in replacement. According to the release notes:

1.1 is fully compatible with the 1.0 release. An
Apache Jackrabbit 1.0 installation can be upgraded by replacing
the relevant jar files with the new versions. No changes to repository
contents are needed.

Sounds like we should do it for the bug fixes alone. The currency issues seems of interest as well. Maybe it scales a little better.

It would be fair that the official 2.6 release of JBoss Portal use the new official jackrabbit 1.1 release.

Olivier.

I think we plan to upgrade it soon.

It has been upgraded in the trunk to version 1.1.1