[
https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639634#action_12639634
]
Jukka Zitting commented on JCR-1808:
------------------------------------
I added a backwards compatibility test case based on your configuration, see
revision 704725.
However, I'm still unable to reproduce the issue. Can you try running the
compatibility test suite I've created? The command sequence is:
svn co
https://svn.apache.org/repos/asf/jackrabbit/sandbox/jackrabbit-test-harness/compatibility
cd compatibility
mvn clean install
This test suite creates a sequence of repositories using different Jackrabbit
versions and repository configurations. I've specified your configuration to be
created using Jackrabbit 1.4. Then the test suite tries to open and access all
those repositories using the latest trunk which at the moment is essentially
the same as 1.5.0-b1.
If the test suite works (i.e. all tests pass) my next option would be to look
at your classpath (mostly the Derby version).
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository
> created with jackrabbit 1.4.*, throws exception on startup. Log output
> included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
