I would just like to refer to http://issues.apache.org/jira/browse/JCR-50 issue which concerns persistence data not being removed properly when deleting a version.
Is it possible to include a fix for this in release 1.0? Yesterday I tracked this issue down and voted for it. I read that it was to be fixed in version 1.0 but today I saw that its fix has been moved for version 1.1. The behaviour I observed regarding this issue is that when I remove a version and print version history, the version appears removed but if the session is closed or the repository is shutdown the version 'miraculously' re-appears if I print the version history again. Regards Giota -----Original Message----- From: Jukka Zitting [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2006 9:57 AM To: jackrabbit-dev@incubator.apache.org Subject: Jackrabbit 1.0 branched Hi, A bit later than originally planned, I've now created the 1.0 branch and postponed a number of remaining issues to 1.1 as described in the Jackrabbit 1.0 release plan. Please let me know if you still want to have some changes included in 1.0. The branch seems to be in a pretty good shape by default and the remaining 1.0 issue (JCR-156) doesn't suggest any explicit changes, so I will make the first release candidate already in the evening. Comments on the issues declared critical in the Jackrabbit 1.0 release plan: [JCR-156] Review test cases and cross check with 1.0 specification This is the only remaining 1.0 issue after the postponing of other open issues. Marcel, can we declare this resolved, or do you want to keep it as a meta-issue? [JCR-215] Code depends on Log4J directly Based on previous email discussions I had hoped for SLF4J 1.0 to be released already now. This is however not the case, so in the interest of avoiding unknown delays I decided to postpone this issue even though I declared it critical in the release plan. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship, JCR consulting, and Java development
