1 |
mdenburger |
46769 |
Running locally |
2 |
|
|
=============== |
3 |
|
|
|
4 |
mdenburger |
46771 |
Checkout and build the following feature branches before building this demo: |
5 |
|
|
|
6 |
|
|
1. CMS restyling branch |
7 |
|
|
|
8 |
|
|
$ svn co https://svn.onehippo.org/repos/hippo/hippo-cms7/cms/branches/cms-restyling |
9 |
|
|
$ cd cms-restyling |
10 |
|
|
$ mvn clean install -DskipTests |
11 |
|
|
|
12 |
mdenburger |
46769 |
This project uses the Maven Cargo plugin to run the CMS and site locally in Tomcat. |
13 |
|
|
From the project root folder, execute: |
14 |
|
|
|
15 |
|
|
$ mvn clean install |
16 |
|
|
$ mvn -P cargo.run |
17 |
|
|
|
18 |
|
|
Access the CMS at http://localhost:8080/cms, and the site at http://localhost:8080/site |
19 |
|
|
Logs are located in target/tomcat7x/logs |
20 |
|
|
|
21 |
|
|
Building distribution |
22 |
|
|
===================== |
23 |
|
|
|
24 |
|
|
To build a Tomcat distribution tarball containing only deployable artifacts: |
25 |
|
|
|
26 |
|
|
$ mvn clean install |
27 |
|
|
$ mvn -P dist |
28 |
|
|
|
29 |
|
|
See also src/main/assembly/distribution.xml if you need to customize the distribution. |
30 |
|
|
|
31 |
|
|
Using JRebel |
32 |
|
|
============ |
33 |
|
|
|
34 |
|
|
Set the environment variable REBEL_HOME to the directory containing jrebel.jar. |
35 |
|
|
|
36 |
|
|
Build with: |
37 |
|
|
|
38 |
|
|
$ mvn clean install -Djrebel |
39 |
|
|
|
40 |
|
|
Start with: |
41 |
|
|
|
42 |
|
|
$ mvn -P cargo.run -Djrebel |
43 |
|
|
|
44 |
|
|
Best Practice for development |
45 |
|
|
============================= |
46 |
|
|
|
47 |
|
|
Use the option -Drepo.path=/some/path/to/repository during start up. This will avoid |
48 |
|
|
your repository to be cleared when you do a mvn clean. |
49 |
|
|
|
50 |
|
|
For example start your project with: |
51 |
|
|
|
52 |
|
|
$ mvn -P cargo.run -Drepo.path=/home/usr/tmp/repo |
53 |
|
|
|
54 |
|
|
or with jrebel: |
55 |
|
|
|
56 |
|
|
$ mvn -P cargo.run -Drepo.path=/home/usr/tmp/repo -Djrebel |
57 |
|
|
|
58 |
|
|
Hot deploy |
59 |
|
|
========== |
60 |
|
|
|
61 |
|
|
To hot deploy, redeploy or undeploy the CMS or site: |
62 |
|
|
|
63 |
|
|
$ cd cms (or site) |
64 |
|
|
$ mvn cargo:redeploy (or cargo:undeploy, or cargo:deploy) |
65 |
|
|
|
66 |
|
|
Automatic Export |
67 |
|
|
================ |
68 |
|
|
|
69 |
|
|
To have your repository changes automatically exported to filesystem during local development, log into |
70 |
|
|
http://localhost:8080/cms/console and press the "Enable Auto Export" button at the top right. To set this |
71 |
|
|
as the default for your project edit the file |
72 |
|
|
./bootstrap/configuration/src/main/resources/configuration/modules/autoexport-module.xml |
73 |
|
|
|
74 |
|
|
Monitoring with JMX Console |
75 |
|
|
=========================== |
76 |
|
|
You may run the following command: |
77 |
|
|
|
78 |
|
|
$ jconsole |
79 |
|
|
|
80 |
|
|
Now open the local process org.apache.catalina.startup.Bootstrap start |