LibreCCM, the Jakarta EE based Web CMS
 
 
 
 
 
 
Go to file
jensp dc1ec63e51 CCM NG/ccm-cms: AssetPane
git-svn-id: https://svn.libreccm.org/ccm/ccm_ng@4661 8810af33-2d31-482b-a856-94f89814c4df
2017-04-05 16:53:44 +00:00
ccm-archetype-module CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-bundle-devel CCM NG: Dependencies for the Devel Bundle are now collected in a separate module which can be used by the bundling modules for the various application servers. 2017-02-14 18:28:25 +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-swarm CCM NG: First part of Wildfly Swarm module 2017-02-14 19:12:45 +00:00
ccm-bundle-devel-wildfly-web CCM NG/ccm-cms: AssetFolderBrowser 2017-04-03 15:54:12 +00:00
ccm-cms CCM NG/ccm-cms: AssetPane 2017-04-05 16:53:44 +00:00
ccm-cms-archetype-contenttype CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-agenda CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-bookmark CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-decisiontree CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-externallink CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-faqitem CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-glossaryitem CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-cms-types-minutes CCM NG: Schema generation is now using Oracle12c dialect instead of Oracle10g dialect. 2017-02-22 18:00:25 +00:00
ccm-core CCM NG/ccm-cms: Next part of AssetPane 2017-03-30 10:44:53 +00:00
ccm-docrepo CCM NG/ccm-core: Removed org.libreccm.formbuilder.WidgetLabel.java. In its current implementation it caused strange problems when querying the database. 2017-03-03 19:45:54 +00:00
ccm-shortcuts CCM NG/ccm-core: Removed org.libreccm.formbuilder.WidgetLabel.java. In its current implementation it caused strange problems when querying the database. 2017-03-03 19:45:54 +00:00
ccm-testutils CCM NG: Fixed several JavaDoc warnings. 2017-02-25 17:06:13 +00:00
ccm-theme-foundry CCM NG/ccm-cms: FolderManipulator Copy/Move (not finished yet). 2017-03-01 19:48:33 +00:00
ccm-xafilesystemadapter CCM NG/ccm-xafilesystemadapter: Fixed some typos in the doc 2017-03-27 18:45:56 +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 [FEATURE] 2016-11-21 17:39:45 +00:00
README.txt CCM NG/ccm-core: Managed profile which starts Wildfly automatically. 2017-02-27 13:31:55 +00:00
build-site.sh CCM NG/ccm-cms: BrowsePane migrated to NG APIs 2017-01-20 16:38:39 +00:00
ccm-readme.txt CCM NG: Build helper script: 2017-03-02 18:22:25 +00:00
ccm.sh CCM NG: Build helper script: Subcommand 'run' now checks for empty bundle name. 2017-03-03 09:04:08 +00:00
pom.xml CCM NG: XAFileSystemAdapter 2017-03-27 15:47:08 +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 test site site:stage -P$profile-name

Note: If there are test failures the package goal fails and the site is not
build. The build the site anywhy use

    mvn clean package site site:stage -Dmaven.test.failure.ignore=true

or with a profile

    mvn clean package site site:stage -Dmaven.test.failure.ignore=true -Pwildfly-remote-h2-mem

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 test 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 -am

for example

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

Using the managed profiles (example is for testing):

mvn clean test -Djboss.home=/path/to/wildfly/ -DstartupTimeoutInSeconds=180 -Pwildfly-managed-h2-mem

You might need to increase the timeout.