Binary distribution or building from sources

Using the CMS Container has two flavors: using the binary distribution or building your own release from the sources.

Binary distribution
Using the binaries means that you use the editor environment and the functionality of the portlets as out-of-the-box functionality. You can add your own layout for the pages and views for the portlets. The latest binary release can be downloaded from the download page. See the installation guide in the documentation section on how to install the binary.

Building from sources
When you plan for adding functionality to the Editor environment or the portlets, or add new portlets or components yourself, you have to build the CMS Container from the sources yourself. The CMS Container is build on top of MMBase and its sources can be found in SVN. The build is based on Maven. CMSc version 1.1 up to 1.6 is using maven 1.1; while CMSc 1.7 and higher use Maven 2 (2.2.1 for example). JDK 1.5 or higher can be used.

binary distributions

Release 1.7

Date: January, 2010
A changelog can be found at the JIRA system, login as guest/guest.
[DOWNLOAD]

2010/02/09 09:54

Release 1.6

Date: May, 2009
A changelog can be found at the JIRA system, login as guest/guest.
[please use 1.7 instead!]
[RELEASE NOTES]

2010/02/09 14:24

Release 1.5

Date: November, 2008
A changelog can be found at the JIRA system, login as guest/guest.
[DOWNLOAD]
[RELEASE NOTES]

2008/12/23 17:18

source repository

General instructions

The source code of the CMS Container is accessible from the MMBase SVN repository.

Checkouts can be done using the following line:
svn co https://scm.mmbase.org/CMSContainer/trunk HEAD

The stable branches can be found as follows:
svn co https://scm.mmbase.org/CMSContainer/branches/b1_7 1_7

2007/04/21 13:49

Dependencies required by CMS Container

In order to run the CMS Container, you have to add some extra jars from other projects to your Tomcat installation. Also see the install documentation in the documentation section. To save time, the third party jars which CMS Container is dependent are listed below, together with their download link.

Before downloading, please read the licensing information that is associated with each downloadable file. The Apache License can be found at http://www.apache.org/licenses/

There is a temporary fix for a known issue with the TomCat 5.5.20 until 5.5.25 releases, which is missing the above classes and therefore doesn't support mail out-of-the-box. For Tomcat 5.5.26+ this is fixed. Extract the following tar file in <tomcat-home>/common/classes: apache-mail-classfiles.tar

For Tomcat 5.5.x: the following files need to be placed in <tomcat-home>/common/lib:

ItemFile
JavaBeans Activation Frameworkactivation-1.1.1.jar or newer

JavaMail APImail-1.4.x.jar

MySQL Connector/Jmysql-connector-java-x.x.xx.bin.jar

Note 1: For Tomcat 6.x: you don't need the activation jar, if you use JDK 1.6.
Note 2: You can also use our prepackaged ZIP which contains those 3 files.

quick links

Download
Quick start guide
Forum
CMSc roadmap (guest / guest)

Download

Want to try CMS Container? Get the latest stable release and sources here!

Latest versions: 1.8.3 & 1.5.14