You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Rama Krishna (JIRA)" <ji...@apache.org> on 2007/09/18 07:52:43 UTC
[jira] Created: (JCR-1139) Upgrading to Jackrabbit 1.3.1 - ERROR
Upgrading to Jackrabbit 1.3.1 - ERROR
-------------------------------------
Key: JCR-1139
URL: https://issues.apache.org/jira/browse/JCR-1139
Project: Jackrabbit
Issue Type: Bug
Components: config
Affects Versions: 1.3.1
Environment: windows
Reporter: Rama Krishna
We are moving from version jackrabbit 1.0 to jackrabbit 1.3.1.
We have replaced following jars:
jackrabbit-api-1.0-4.jar --> jackrabbit-api-1.3.1.jar
jackrabbit-commons-1.0-4.jar --> jackrabbit-core-1.3.1.jar
jackrabbit-core-1.0-4.jar --> jackrabbit-jcr-commons-1.3.1.jar
After replacing these jars my repository not started and also its not showing any error.
RepositoryConfig.create --> returning null
Please advise.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1139) Upgrading to Jackrabbit 1.3.1 - ERROR
Posted by "Rama Krishna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rama Krishna updated JCR-1139:
------------------------------
Attachment: repository.xml
RepositoryServlet.java
jaas.config
my app config files
> Upgrading to Jackrabbit 1.3.1 - ERROR
> -------------------------------------
>
> Key: JCR-1139
> URL: https://issues.apache.org/jira/browse/JCR-1139
> Project: Jackrabbit
> Issue Type: Bug
> Components: config
> Affects Versions: 1.3.1
> Environment: windows
> Reporter: Rama Krishna
> Attachments: jaas.config, repository.xml, RepositoryServlet.java
>
>
> We are moving from version jackrabbit 1.0 to jackrabbit 1.3.1.
> We have replaced following jars:
> jackrabbit-api-1.0-4.jar --> jackrabbit-api-1.3.1.jar
> jackrabbit-commons-1.0-4.jar --> jackrabbit-core-1.3.1.jar
> jackrabbit-core-1.0-4.jar --> jackrabbit-jcr-commons-1.3.1.jar
> After replacing these jars my repository not started and also its not showing any error.
> RepositoryConfig.create --> returning null
> Please advise.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1139) Upgrading to Jackrabbit 1.3.1 - ERROR
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1139.
--------------------------------
Resolution: Invalid
Assignee: Jukka Zitting
What's the 1.0-4 version you were using earlier? The jackrabbit-api component was first introduced in Jackrabbit 1.2.
Did you upgrade the Lucene dependency to version 2.0?
See also the "Upgrading to Jackrabbit 1.2" and "Upgrading to Jackrabbit 1.3" sections in the release notes for more details on the upgrades.
I'm resolving this issue as Invalid, please use the users@jackrabbit.apache.org mailing list for support questions. The issue tracker should only be used if you've already identified a specific issue in Jackrabbit.
> Upgrading to Jackrabbit 1.3.1 - ERROR
> -------------------------------------
>
> Key: JCR-1139
> URL: https://issues.apache.org/jira/browse/JCR-1139
> Project: Jackrabbit
> Issue Type: Bug
> Components: config
> Affects Versions: 1.3.1
> Environment: windows
> Reporter: Rama Krishna
> Assignee: Jukka Zitting
> Attachments: jaas.config, repository.xml, RepositoryServlet.java
>
>
> We are moving from version jackrabbit 1.0 to jackrabbit 1.3.1.
> We have replaced following jars:
> jackrabbit-api-1.0-4.jar --> jackrabbit-api-1.3.1.jar
> jackrabbit-commons-1.0-4.jar --> jackrabbit-core-1.3.1.jar
> jackrabbit-core-1.0-4.jar --> jackrabbit-jcr-commons-1.3.1.jar
> After replacing these jars my repository not started and also its not showing any error.
> RepositoryConfig.create --> returning null
> Please advise.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.