-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
71 lines (43 loc) · 1.64 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Running locally
===============
This project uses the Maven Cargo plugin to run the CMS and site locally in Tomcat.
From the project root folder, execute:
$ mvn clean install
$ mvn -P cargo.run
Access the CMS at http://localhost:8080/cms, and the site at http://localhost:8080/site
Logs are located in target/tomcat6x/logs
Building distribution
=====================
To build a Tomcat distribution tarball containing only deployable artifacts:
$ mvn clean install
$ mvn -P dist
See also src/main/assembly/distribution.xml if you need to customize the distribution
Using JRebel
============
Set the environment variable REBEL_HOME to the directory containing jrebel.jar.
Build with:
$ mvn clean install -Djrebel
Start with:
$ mvn -P cargo.run -Djrebel
Best Practice for development
============
Use the option -Drepo.path=/some/path/to/repository during start up. This will avoid
your repository to be cleared when you do a mvn clean.
For example start your project with:
$ mvn -P cargo.run -Drepo.path=/home/usr/tmp/repo
or with jrebel:
$ mvn -P cargo.run -Drepo.path=/home/usr/tmp/repo -Djrebel
Hot deploy
==========
To hot deploy, redeploy or undeploy the CMS or site:
$ cd cms (or site)
$ mvn cargo:redeploy (or cargo:undeploy, or cargo:deploy)
Automatic Export
==========
Changes to your repository are automatically exported to filesystem during local development, to disable this feature,
log into the console and press "disable auto export".
Monitoring with JMX Console
===========================
You may run the following command:
$ jconsole
Now open the local process org.apache.catalina.startyp.Bootstrap start