LibreCCM, the Jakarta EE based Web CMS
 
 
 
 
 
 
Go to file
jensp 02064601f8 CCM NG: ContentItemManager bug fixes for copy method
git-svn-id: https://svn.libreccm.org/ccm/ccm_ng@4298 8810af33-2d31-482b-a856-94f89814c4df
2016-09-13 12:51:31 +00:00
ccm-archetype-module CCM NG: Adjusted several poms and tests 2016-05-13 15:18:46 +00:00
ccm-bundle-devel-wildfly CCM NG: Increased timeout for wildfly-maven-plugin 2016-08-11 16:35:38 +00:00
ccm-bundle-devel-wildfly-web CCM NG: 2016-08-15 18:14:48 +00:00
ccm-cms CCM NG: ContentItemManager bug fixes for copy method 2016-09-13 12:51:31 +00:00
ccm-cms-archetype-contenttype CCM NG: Adjusted several poms and tests 2016-05-13 15:18:46 +00:00
ccm-cms-types-agenda CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-bookmark CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-decisiontree CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-externallink CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-faqitem CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-glossaryitem CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-cms-types-minutes CCM NG: It is now possible to run the development bundle in a Wildfly application server using Maven. 2016-06-03 14:41:05 +00:00
ccm-core CCM NG: Added references from Workflow to the WorkflowTemplate used to create the workflow. 2016-09-12 15:44:45 +00:00
ccm-docrepo adds testfiles to filePortationTest 2016-06-07 14:54:17 +00:00
ccm-shortcuts CCM NG: Workflow and Lifecycle managment 2016-08-10 15:06:05 +00:00
ccm-testutils CCM NG: Files etc for testing ContentSectionManager 2016-07-15 18:06:32 +00:00
ccm-theme-foundry CCM NG: 2016-04-21 16:44:41 +00:00
src/site CCM NG: Code conventions page now states Java 8 as target language. 2016-08-30 11:41:33 +00:00
.svnignore - adds svnignore for *.log files 2015-10-01 10:00:40 +00:00
README.txt CCM NG: Extended the README file. 2016-08-30 15:30:17 +00:00
pom.xml CCM NG: Basic part of Hibernate Search integration 2016-08-12 18:20:34 +00:00

README.txt

LibreCCM
========

The documentation of project is provided as Maven project site. To
create the site run

    mvn package site site:stage

and open the file ./target/staging/index.html in your browser.

To recreate the site run

    mvn clean package site site:stage

To include integration tests into the reports

    mvn clean package site site:stage -P$profile-name

The available profiles are listed in the documentation. All modules should 
provide a profile called wildfly-remote-h2-mem. This profile uses a remote
Wildfly application server and its integrated H2 in-memory database for
running the tests. Before you can run the integration tests you must download
Wildfly from http://www.wildfly.org. Unzip the downloaded archive and start
the server using the bin/standalone.sh file. Then go to another terminal,
navigate to the CCM NG directory and run

    mvn clean package site site:stage -Pwildfly-remote-h2-mem

To run LibreCCM choose the bundle to run, for instance
ccm-bundle-devel-wildfly. Depending on the bundle and the selected profile 
you may have to configure a datasource in the Wildfly server and create a
database. Also you need to configure an environement variable which points to
your Wildfly installation. Then you can run LibreCCM using

    mvn package wildfly:run -DskipTests -pl ccm-bundle-devel-wildfly -am -Pgeneric

The above example skips all tests to speed up the start process. The generic
profile used in this example uses an existing Wildfly installation. The
JBOSS_HOME environment variable must either be configured or must be provided.
Alternativly you can provide the location of your Wildfly installation using
the -D switch: mvn -Djboss-as.home=/path/to/wildfly/

To install the archetypes in your local Maven repository run

    mvn [clean] install -pl $archetype-module

for example

mvn clean install -pl ccm-cms-archetypes-contenttype