JCR-52: Provide a JCR Repository Service which allow 'binding' hippo-jcr-console to a separate JCR Repository in another web application - change of plan: Instead of using a shared classloader JCR Repository Service, a cross-context Repository instance lookup will be used based on the standard JackrabitRepositoryServlet and ContextRepositoryServlet. Extended versions of these servlets will be used to support system property configurations for setting repository home, location and (server provider application) context path. Furthermore, as no shared classloader module is needed anymore, the jr-repository-servlet module will be merged into the jcr-repository-service and thereafter dropped. - also: bump to latest Jackrabbit 2.4
JCR-56: Rename project and module artifact names to use hippo- prefix
JCR-55: Move Hippo JCR Console project svn location from /experimental to new /hippo-jcr svn parent
JCR-25: move all jcr-repo-console modules up to the jcr-console root project - rename jcr-repo-console-* modules to jcr-console (jcr already means 'java content repository', no need to say it twice) - hippo-console sub module is aggregated, but "detached" by using a different/independent parent - rename war module artifact final name to jcr-console to distinguish it from the hippo-console (which was likewise renamed)
JCR-25: cloning all Hippo Console modules as sibling JCR Console modules; refining pom.xml files
JCR-25: cloning all Hippo Console modules as sibling JCR Console modules
JCR-24: changing war name from cms to console
JCR-24: using the default cms app configuration for now, in order to try running the application
JCR-24: refining dependencies and cargo configurations
JCR-24: adding war subproject with cargo plugin configuration
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.