You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/10/15 01:54:46 UTC
[jira] Resolved: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1808.
--------------------------------
Resolution: Invalid
Assignee: Jukka Zitting
No, the configuration is an essential part of the repository throughout its life.
1.5.0-b1 surfaced some backwards compatibility issues with old repository configurations, but those should all now be resolved (in trunk and the 1.5 branch). The configuration you used to create a repository should work as-is on any later Jackrabbit 1.x 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
> Assignee: Jukka Zitting
> 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.