[13798] hippo-ecm/trunk/src/site: HREPTWO-1250 - more renaming of folders
|
View:
New views
1 Messages
—
Rating Filter:
Alert me
|
 |
[13798] hippo-ecm/trunk/src/site: HREPTWO-1250 - more renaming of folders
by svn-logs
::
Rate this Message:
Revision: 13798
Author: nvankampenhout Date: 2008-10-07 01:20:31 +0200 (Tue, 07 Oct 2008) Log Message: ----------- HREPTWO-1250 - more renaming of folders Modified Paths: -------------- hippo-ecm/trunk/src/site/site.xml hippo-ecm/trunk/src/site/xdoc/about-hippo-ecm/architecture.xml hippo-ecm/trunk/src/site/xdoc/delve_into/development/project-structure.xml hippo-ecm/trunk/src/site/xdoc/delve_into/directions.xml hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/facets/facetsearch.xml hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/searching.xml hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/index.xml Added Paths: ----------- hippo-ecm/trunk/src/site/xdoc/delve_into/extension/ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/document-types/ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml hippo-ecm/trunk/src/site/xdoc/delve_into/extension/plugins/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/jcr/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/toolkits/ Removed Paths: ------------- hippo-ecm/trunk/src/site/xdoc/delve_into/extension/document-templates/ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml hippo-ecm/trunk/src/site/xdoc/delve_into/extension/plugins/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/jcr/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/reference/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/toolkits/ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/website-development/ Modified: hippo-ecm/trunk/src/site/site.xml =================================================================== --- hippo-ecm/trunk/src/site/site.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/site.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -146,36 +146,36 @@ </item> </item> - <item name="CMS Implement Guide" href="/delve_into/implement-hippo-ecm/index.html" collapse="true"> - <item name="Toolkits" href="/delve_into/implement-hippo-ecm/toolkits/index.html"/> - <item name="JCR Interface" href="/delve_into/implement-hippo-ecm/jcr/index.html" collapse="true"> - <item name="Basics" href="/delve_into/implement-hippo-ecm/jcr/jcr.html"/> - <item name="Examples" href="/delve_into/implement-hippo-ecm/jcr/examples.html"/> - <item name="Importing Content" href="/delve_into/implement-hippo-ecm/jcr/importing-content.html"/> + <item name="CMS Implement Guide" href="/delve_into/implementation/index.html" collapse="true"> + <item name="Toolkits" href="/delve_into/implementation/toolkits/index.html"/> + <item name="JCR Interface" href="/delve_into/implementation/jcr/index.html" collapse="true"> + <item name="Basics" href="/delve_into/implementation/jcr/jcr.html"/> + <item name="Examples" href="/delve_into/implementation/jcr/examples.html"/> + <item name="Importing Content" href="/delve_into/implementation/jcr/importing-content.html"/> </item> - <!--<item name="Dropbox Example" href="/delve_into/implement-hippo-ecm/advanced/jcr-dropbox-example.html"/>--> + <!--<item name="Dropbox Example" href="/delve_into/implementation/advanced/jcr-dropbox-example.html"/>--> </item> - <item name="CMS Extension Guide" href="/delve_into/extend-hippo-ecm/index.html" collapse="true"> - <item name="Document Types" href="/delve_into/extend-hippo-ecm/document-types/index.html" collapse="true"> - <item name="Type Editor" href="/delve_into/extend-hippo-ecm/document-types/editor.html" /> - <item name="Tutorial" href="/delve_into/extend-hippo-ecm/document-types/tutorial.html" /> - <item name="Examples" href="/delve_into/extend-hippo-ecm/document-types/examples.html" /> - <item name="Field Types" href="/delve_into/extend-hippo-ecm/document-types/fieldtypes.html" /> - <item name="Advanced" href="/delve_into/extend-hippo-ecm/document-types/advanced.html" /> + <item name="CMS Extension Guide" href="/delve_into/extension/index.html" collapse="true"> + <item name="Document Types" href="/delve_into/extension/document-types/index.html" collapse="true"> + <item name="Type Editor" href="/delve_into/extension/document-types/editor.html" /> + <item name="Tutorial" href="/delve_into/extension/document-types/tutorial.html" /> + <item name="Examples" href="/delve_into/extension/document-types/examples.html" /> + <item name="Field Types" href="/delve_into/extension/document-types/fieldtypes.html" /> + <item name="Advanced" href="/delve_into/extension/document-types/advanced.html" /> </item> - <item name="Add-ons" href="/delve_into/extend-hippo-ecm/plugins/index.html" collapse="true"> - <item name="Repository Plugins" href="/delve_into/extend-hippo-ecm/plugins/repository/index.html"> - <item name="Workflow" href="/delve_into/extend-hippo-ecm/plugins/repository/workflow.html"/> + <item name="Add-ons" href="/delve_into/extension/plugins/index.html" collapse="true"> + <item name="Repository Plugins" href="/delve_into/extension/plugins/repository/index.html"> + <item name="Workflow" href="/delve_into/extension/plugins/repository/workflow.html"/> </item> - <item name="Frontend Plugins" href="/delve_into/extend-hippo-ecm/plugins/frontend/index.html" collapse="true"> - <item name="Architecture" href="/delve_into/extend-hippo-ecm/plugins/frontend/frontend-plugin-architecture.html"/> - <item name="Communication" href="/delve_into/extend-hippo-ecm/plugins/frontend/frontend-plugin-communication.html"/> - <item name="Skin" href="/delve_into/extend-hippo-ecm/plugins/frontend/frontend-plugin-skin.html"/> - <item name="Hello World" href="/delve_into/extend-hippo-ecm/plugins/frontend/hello-world.html"/> + <item name="Frontend Plugins" href="/delve_into/extension/plugins/frontend/index.html" collapse="true"> + <item name="Architecture" href="/delve_into/extension/plugins/frontend/frontend-plugin-architecture.html"/> + <item name="Communication" href="/delve_into/extension/plugins/frontend/frontend-plugin-communication.html"/> + <item name="Skin" href="/delve_into/extension/plugins/frontend/frontend-plugin-skin.html"/> + <item name="Hello World" href="/delve_into/extension/plugins/frontend/hello-world.html"/> </item> </item> - <item name="Packaging" href="/delve_into/extend-hippo-ecm/packaging.html"/> + <item name="Packaging" href="/delve_into/extension/packaging.html"/> </item> <item name="CMS Develop Guide" href="/delve_into/development/index.html" collapse="true"> Modified: hippo-ecm/trunk/src/site/xdoc/about-hippo-ecm/architecture.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/about-hippo-ecm/architecture.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/about-hippo-ecm/architecture.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -102,7 +102,7 @@ can integrate with any application, new or existing, as long as it uses the JCR API. Examples of applications that can integrate with Hippo ECM are email and calendar software, data import and export, wikis, blogs. Details and examples are - given in the <a href="../delve_into/implement-hippo-ecm/jcr/index.html">JCR Interface</a> section. + given in the <a href="../delve_into/implementation/jcr/index.html">JCR Interface</a> section. </p> </subsection> Modified: hippo-ecm/trunk/src/site/xdoc/delve_into/development/project-structure.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/development/project-structure.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/development/project-structure.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -130,7 +130,7 @@ <p> The large number of projects is a direct consequence of the fact that Hippo ECM has been designed from the ground up for customizability and extendability as described in the - <a href="../extend-hippo-ecm/plugins/index.html">plugin</a> documentation. The repository and frontend + <a href="../extension/plugins/index.html">plugin</a> documentation. The repository and frontend engines that make up the core of Hippo ECM don't implement much functionality themselves. All 'userland' functionality is implemented by plugins that are loaded by the engines. See the chapter on <a href="../run-hippo-ecm/repository-bootstrap.html">Bootstrapping the repository</a> for @@ -205,7 +205,7 @@ These are the addons that bundle the high level plugins that make up a user application. For the CMS these are the addons under <b>addon-cms</b>. Frontend plugins can interact with each other via the plugin - <a href="../extend-hippo-ecm/plugins/frontend/frontend-plugin-communication.html">communication model</a> + <a href="../extension/plugins/frontend/frontend-plugin-communication.html">communication model</a> offered by the frontend engine. <br/><br/> Modified: hippo-ecm/trunk/src/site/xdoc/delve_into/directions.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/directions.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/directions.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -70,10 +70,10 @@ </tr> <tr> <td> - <a href="run-hippo-ecm/index.html"><em><img alt="run" src="../images/frontpage/run.png" /></em></a> + <a href="admin/index.html"><em><img alt="run" src="../images/frontpage/run.png" /></em></a> </td> <td> - <a href="run-hippo-ecm/index.html"><em>CMS Admin Guide</em></a> + <a href="admin/index.html"><em>CMS Admin Guide</em></a> </td> <td> For system administrators, for installing and configuring to integrate in your system. @@ -90,11 +90,11 @@ </tr> <tr> <td> - <a href="implement-hippo-ecm/index.html"><em><img alt="implement" src="../images/frontpage/implement.png" /></em> + <a href="implementation/index.html"><em><img alt="implement" src="../images/frontpage/implement.png" /></em> </a> </td> <td> - <a href="implement-hippo-ecm/index.html"><em>CMS Implement Guide</em></a> + <a href="implementation/index.html"><em>CMS Implement Guide</em></a> </td> <td> </td> @@ -110,10 +110,10 @@ </tr> <tr> <td> - <a href="extend-hippo-ecm/index.html"><em><img alt="extend" src="../images/frontpage/extend.png" /></em></a> + <a href="extension/index.html"><em><img alt="extend" src="../images/frontpage/extend.png" /></em></a> </td> <td> - <a href="extend-hippo-ecm/index.html"><em>CMS Extension Guide</em></a> + <a href="extension/index.html"><em>CMS Extension Guide</em></a> </td> <td> For developers of custom plugins such as for extra properties @@ -122,10 +122,10 @@ </tr> <tr> <td> - <a href="building/index.html"><em><img alt="build" src="../images/frontpage/build.png" /></em></a> + <a href="development/index.html"><em><img alt="build" src="../images/frontpage/build.png" /></em></a> </td> <td> - <a href="building/index.html"><em>CMS Develop Guide</em></a> + <a href="development/index.html"><em>CMS Develop Guide</em></a> </td> <td> For Hippo CMS core developers, who develop the CMS core engines and the CMS core plugins and Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/extension (from rev 13795, hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm) Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/document-types (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/document-types) Deleted: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/index.xml 2008-10-06 22:17:06 UTC (rev 13795) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE document PUBLIC - "-//Apache Software Foundation//DTD XDOC 1.0//EN" - "http://maven.apache.org/dtd/xdoc_1_0.dtd"> -<!-- - Copyright 2007 Hippo - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" - BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> -<document> - <properties> - <title>Extension Guide</title> - </properties> - <body> - <section name="Extension Guide"> - - <p> - Hippo CMS provides a full enterprise content management system that - can be used straight out of the box. Should the default functionality - however not suit your organization's needs, then its open - component based architecture allows for easy customization and extension - of the system. - </p> - - <ul> - <li> - <a href="document-templates/index.html">Document Types</a> - - Customize the Hippo ECM document types or create your own - </li> - <li> - <a href="plugins/index.html">Add-ons</a> - - Extend Hippo ECM with your own add-ons. - </li> - <li> - <a href="packaging.html">Custom Packaging</a> - - Create a custom war file on top of the quickstart war - </li> - </ul> - - </section> - </body> -</document> \ No newline at end of file Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/index.xml) =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml (rev 0) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/index.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -0,0 +1,52 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE document PUBLIC + "-//Apache Software Foundation//DTD XDOC 1.0//EN" + "http://maven.apache.org/dtd/xdoc_1_0.dtd"> +<!-- + Copyright 2007 Hippo + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" + BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>Extension Guide</title> + </properties> + <body> + <section name="Extension Guide"> + + <p> + Hippo CMS provides a full enterprise content management system that + can be used straight out of the box. Should the default functionality + however not suit your organization's needs, then its open + component based architecture allows for easy customization and extension + of the system. + </p> + + <ul> + <li> + <a href="document-types/index.html">Document Types</a> + - Customize the Hippo ECM document types or create your own + </li> + <li> + <a href="plugins/index.html">Add-ons</a> + - Extend Hippo ECM with your own add-ons. + </li> + <li> + <a href="packaging.html">Custom Packaging</a> + - Create a custom war file on top of the quickstart war + </li> + </ul> + + </section> + </body> +</document> \ No newline at end of file Deleted: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/packaging.xml 2008-10-06 22:17:06 UTC (rev 13795) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -1,142 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE document PUBLIC - "-//Apache Software Foundation//DTD XDOC 1.0//EN" - "http://maven.apache.org/dtd/xdoc_1_0.dtd"> -<!-- - Copyright 2007 Hippo - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" - BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> -<document> - <properties> - <title>Custom packaging</title> - </properties> - <body> - <section name="Creating your own war package"> - <p> - In the <a href="plugins/frontend/hello-world.html">Hello World</a> example we created a plugin and included - it directly in the quickstart war project. - While this works just fine, it requires you to make changes to an external project, and if there are a lot - of changes to be made it can get messy. - It would be better if we can just leave quickstart war untouched and build our own war using quickstart war - as a blue print. - </p> - </section> - <section name="Your own pom file"> - <p> - All there is to creating your own war file is some modifications to the pom file (of your own project). - </p> - <p> - <b>Note:</b> It is assumed that you have a project with a pom file similar to the one created in the - <a href="plugins/frontend/hello-world.html">Hello World</a> tutorial. - If you don't have that you are better off following that tutorial first. - </p> - <subsection name="Adding the war dependency"> - <p> - First we need to add a dependency to the quickstart war to our pom file. - </p> - <source> -<dependency> - <groupId>org.hippoecm</groupId> - <artifactId>hippo-ecm-quickstart</artifactId> - <version>2.01.00.13536</version> - <type>war</type> - <scope>runtime</scope> -</dependency> -</source> - </subsection> - <subsection name="Modifying the build section"> - <p> - Add the following to the plugins section. It tells maven to use the quickstart war as an overlay. - </p> - <source> -<plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-war-plugin</artifactId> - <version>2.1-alpha-1</version> - <configuration> - <overlays> - <overlay> - <groupId>org.hippoecm</groupId> - <artifactId>hippo-ecm-quickstart</artifactId> - </overlay> - </overlays> - </configuration> -</plugin> -</source> - <p> - Well thats actually it. Running <b>mvn install</b> will create a custom war of your own plugin project and store it in the maven repository. - </p> - </subsection> - <subsection name="Troubleshooting"> - <p> - It can happen that maven is unable to find the quickstart war. In that case it will print instructions on how to add the the file to your repository. - You will probably have to do this if you only downloaded the war instead of building it yourself with maven. - </p> - </subsection> - </section> - <section name="Adding the jetty plugin for fast testing"> - <p> - While developing your plugin you will probably what to test your work a lot. So lets take a moment to make that easy. - You can add the jetty plugin to your pom file which will make it very easy to get your plugin running fast. - </p> - <p> - Add the following plugin section to your plugins section in your pom file. - You will now be able to test drive your war with <b>mvn jetty:run-war</b>. - </p> - <source> -<plugin> - <groupId>org.mortbay.jetty</groupId> - <artifactId>maven-jetty-plugin</artifactId> - <version>6.1.10</version> - <configuration> - <scanIntervalSeconds>5</scanIntervalSeconds> - <connectors> - <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector"> - <port>8080</port> - </connector> - </connectors> - <contextPath>/cms</contextPath> - </configuration> - <dependencies> - <!-- atomikos dependecies for running jetty:run[-war|-exploded] --> - <dependency> - <groupId>com.atomikos</groupId> - <artifactId>transactions-api</artifactId> - <version>3.1.4</version> - <scope>runtime</scope> - </dependency> - <dependency> - <groupId>com.atomikos</groupId> - <artifactId>transactions-jta</artifactId> - <version>3.1.4</version> - <scope>runtime</scope> - </dependency> - <dependency> - <groupId>com.atomikos</groupId> - <artifactId>transactions</artifactId> - <version>3.1.4</version> - <scope>runtime</scope> - </dependency> - <dependency> - <groupId>com.atomikos</groupId> - <artifactId>atomikos-util</artifactId> - <version>3.1.4</version> - <scope>runtime</scope> - </dependency> - </dependencies> -</plugin> - </source> - </section> - </body> -</document> \ No newline at end of file Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/packaging.xml) =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml (rev 0) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/extension/packaging.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -0,0 +1,142 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE document PUBLIC + "-//Apache Software Foundation//DTD XDOC 1.0//EN" + "http://maven.apache.org/dtd/xdoc_1_0.dtd"> +<!-- + Copyright 2007 Hippo + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" + BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>Custom packaging</title> + </properties> + <body> + <section name="Creating your own war package"> + <p> + In the <a href="plugins/frontend/hello-world.html">Hello World</a> example we created a plugin and included + it directly in the quickstart war project. + While this works just fine, it requires you to make changes to an external project, and if there are a lot + of changes to be made it can get messy. + It would be better if we can just leave quickstart war untouched and build our own war using quickstart war + as a blue print. + </p> + </section> + <section name="Your own pom file"> + <p> + All there is to creating your own war file is some modifications to the pom file (of your own project). + </p> + <p> + <b>Note:</b> It is assumed that you have a project with a pom file similar to the one created in the + <a href="plugins/frontend/hello-world.html">Hello World</a> tutorial. + If you don't have that you are better off following that tutorial first. + </p> + <subsection name="Adding the war dependency"> + <p> + First we need to add a dependency to the quickstart war to our pom file. + </p> + <source> +<dependency> + <groupId>org.hippoecm</groupId> + <artifactId>hippo-ecm-quickstart</artifactId> + <version>2.01.00.13536</version> + <type>war</type> + <scope>runtime</scope> +</dependency> +</source> + </subsection> + <subsection name="Modifying the build section"> + <p> + Add the following to the plugins section. It tells maven to use the quickstart war as an overlay. + </p> + <source> +<plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-war-plugin</artifactId> + <version>2.1-alpha-1</version> + <configuration> + <overlays> + <overlay> + <groupId>org.hippoecm</groupId> + <artifactId>hippo-ecm-quickstart</artifactId> + </overlay> + </overlays> + </configuration> +</plugin> +</source> + <p> + Well thats actually it. Running <b>mvn install</b> will create a custom war of your own plugin project and store it in the maven repository. + </p> + </subsection> + <subsection name="Troubleshooting"> + <p> + It can happen that maven is unable to find the quickstart war. In that case it will print instructions on how to add the the file to your repository. + You will probably have to do this if you only downloaded the war instead of building it yourself with maven. + </p> + </subsection> + </section> + <section name="Adding the jetty plugin for fast testing"> + <p> + While developing your plugin you will probably what to test your work a lot. So lets take a moment to make that easy. + You can add the jetty plugin to your pom file which will make it very easy to get your plugin running fast. + </p> + <p> + Add the following plugin section to your plugins section in your pom file. + You will now be able to test drive your war with <b>mvn jetty:run-war</b>. + </p> + <source> +<plugin> + <groupId>org.mortbay.jetty</groupId> + <artifactId>maven-jetty-plugin</artifactId> + <version>6.1.10</version> + <configuration> + <scanIntervalSeconds>5</scanIntervalSeconds> + <connectors> + <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector"> + <port>8080</port> + </connector> + </connectors> + <contextPath>/cms</contextPath> + </configuration> + <dependencies> + <!-- atomikos dependecies for running jetty:run[-war|-exploded] --> + <dependency> + <groupId>com.atomikos</groupId> + <artifactId>transactions-api</artifactId> + <version>3.1.4</version> + <scope>runtime</scope> + </dependency> + <dependency> + <groupId>com.atomikos</groupId> + <artifactId>transactions-jta</artifactId> + <version>3.1.4</version> + <scope>runtime</scope> + </dependency> + <dependency> + <groupId>com.atomikos</groupId> + <artifactId>transactions</artifactId> + <version>3.1.4</version> + <scope>runtime</scope> + </dependency> + <dependency> + <groupId>com.atomikos</groupId> + <artifactId>atomikos-util</artifactId> + <version>3.1.4</version> + <scope>runtime</scope> + </dependency> + </dependencies> +</plugin> + </source> + </section> + </body> +</document> \ No newline at end of file Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/extension/plugins (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/extend-hippo-ecm/plugins) Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/implementation (from rev 13790, hippo-ecm/trunk/src/site/xdoc/delve_into/implement-hippo-ecm) Deleted: hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/implement-hippo-ecm/index.xml 2008-10-06 14:53:03 UTC (rev 13790) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE document PUBLIC - "-//Apache Software Foundation//DTD XDOC 1.0//EN" - "http://maven.apache.org/dtd/xdoc_1_0.dtd"> -<!-- - Copyright 2007 Hippo - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" - BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> -<document> - <properties> - <title>Implementing Hippo ECM</title> - </properties> - <body> - <section name="Implementing Hippo ECM"> - - <p> - While Hippo ECM can be used out of the box to manage your content, implementing - the system in your unique environment will require some work. This section directs - you to the right tools, and explains how to access your content through the - repository's JCR interface. - </p> - - <ul> - <li> - <a href="toolkits/index.html">Toolkits</a> - - Learn about toolkits that help you implement website, portals, etc. using Hippo CMS. - </li> - <li> - <a href="jcr/index.html">JCR Interface</a> - - Access your content through the standard JCR interface. - </li> - </ul> - - </section> - </body> -</document> \ No newline at end of file Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/implement-hippo-ecm/index.xml) =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml (rev 0) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/index.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -0,0 +1,53 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE document PUBLIC + "-//Apache Software Foundation//DTD XDOC 1.0//EN" + "http://maven.apache.org/dtd/xdoc_1_0.dtd"> +<!-- + Copyright 2007 Hippo + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" + BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>Implementation Guide</title> + </properties> + <body> + <section name="Implementation Guide"> + + <p> + While Hippo CMS can be used out of the box to manage your content, implementing + the system in your unique environment requires some work. You will have to + set up a front end application (website, intranet, portal) to publish your + content to. You want to know how to integrate Hippo CMS in your enviroment. + This section directs + you to the right tools, and explains how to access your content through the + repository's JCR interface. + </p> + + <ul> + <li> + <a href="toolkits/index.html">Toolkits</a> + - Using one of the available toolkits is the recommended way to implement + Hippo CMS. The toolkits help you create websites and portals using the + technology of your choice. + </li> + <li> + <a href="jcr/index.html">JCR Interface</a> + - Access your content through the standard JCR interface. This will give + you direct access and offers almost unlimited possibilities. + </li> + </ul> + + </section> + </body> +</document> \ No newline at end of file Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/jcr (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/implement-hippo-ecm/jcr) Copied: hippo-ecm/trunk/src/site/xdoc/delve_into/implementation/toolkits (from rev 13797, hippo-ecm/trunk/src/site/xdoc/delve_into/implement-hippo-ecm/toolkits) Modified: hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/facets/facetsearch.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/facets/facetsearch.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/facets/facetsearch.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -34,9 +34,9 @@ nodes. These representations are again exposed as 'normal' JCR nodes (according to JSR-170 specification), and can be used to represent all kinds of data in all kinds of different structures purely defined by their meta information. This results in virtual node trees - providing a faceted navigation. See the - <a href="../../implement-hippo-ecm/advanced/jcr-dropbox-example.html">example</a> - for a ready to use demo project creating faceted navigation. + providing a faceted navigation. <!--See the + <a href="../../implementation/advanced/jcr-dropbox-example.html">example</a> + for a ready to use demo project creating faceted navigation.--> </p> <subsection name="Faceted navigation explained: visual"> <p> Modified: hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/searching.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/searching.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/hippo-ecm-concepts/searching.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -60,7 +60,7 @@ <subsection name="How to use a stored search/query"> <p> A frontend can execute a query node to get the actual search result. The - <a href="../../implement-hippo-ecm/website-development/index.html">Hippo Site Toolkit</a> automatically + <a href="../../implementation/toolkits/index.html">Hippo Site Toolkit</a> automatically detects a search node, executes the search and let you navigate through the result set. </p> </subsection> @@ -70,7 +70,7 @@ want to reuse the same search but only tune a parameter, like the number of results you want. Therefor, we support parameterized queries. This means that at some place in the query, a '$' can be placed, which is substituted by a value during execution. - See <a href="../../implement-hippo-ecm/website-development/index.html">Hippo Site Toolkit</a> + See <a href="../../implementation/toolkits/index.html">Hippo Site Toolkit</a> on how you can use this. </p> </subsection> Modified: hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/index.xml =================================================================== --- hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/index.xml 2008-10-06 22:58:41 UTC (rev 13797) +++ hippo-ecm/trunk/src/site/xdoc/delve_into/use-hippo-ecm/index.xml 2008-10-06 23:20:31 UTC (rev 13798) @@ -59,7 +59,7 @@ <subsection name="Hippo CMS 7"> <p> Hippo CMS 7 is the frontend application. It is implemented with <a href="http://wicket.apache.org">Apache Wicket</a> using - a <a href="../extend-hippo-ecm/plugins/index.html">custom plugin framework</a> which is configured in Hippo Repository. + a <a href="../extension/plugins/index.html">custom plugin framework</a> which is configured in Hippo Repository. We have created <a href="tour/index.html">a tour</a> to show you the key concepts you need to know to start using the CMS. </p> </subsection> _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
| Free Forum Powered by Nabble | Forum Help |
