[
https://issues.apache.org/jira/browse/JCR-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-3893:
Fix Version/s: 2.14
> Multiple issues with standalone 2.10.1
> --
[
https://issues.apache.org/jira/browse/JCR-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-3893:
--
Component/s: (was: jackrabbit-jcr-server)
jackrabbit-webapp
> Multiple
[
https://issues.apache.org/jira/browse/JCR-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-3893:
--
Priority: Minor (was: Major)
> Multiple issues with standalone 2.10.1
>
[
https://issues.apache.org/jira/browse/JCR-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-3893:
--
Summary: Multiple issues with standalone 2.10.1 (was: Multiple issues with
standalone 2.10.1 -
I doubt that this would be a Maven issue or classpath issue, since I am just
running the provided jar using the java runtime.
What could be the cause of these diverse issues?
https://issues.apache.org/jira/browse/JCR-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
I think I've seen these types of errors before. It involved (I think) just
having improper (incompatible) sets of dependencies in the maven. Some part
of the dependencies got updated, but now the entire classpath is no longer
workable. For example if you use SpringBoot you know your entire
