Requirements

Cross is implemented in JAVA 7. The source code is available at SourceForge

• Java 7 JDK
• Git
• Apache Maven, and/or an IDE with integrated Maven support

Building Cross from Source

The sourcecode of Cross is under control of the distributed version control system Git. In order to access the latest source, you need to clone the repository to your local system:

git clone git://git.code.sf.net/p/maltcmscross/code maltcmscross-code

Other software for working with Git should work similarly.

After checking out, you will find the root maven module cross below maltcmscross-code. Run

mvn install

from the command line to build the complete project, to run the corresponding unit tests, and to install the generated artifacts into your local maven repository.

Using Cross as a Library

The modules of Cross are published as maven artifacts, hosted by a custom Artifactory instance at Maltcms Artifactory.

To add the Maltcms Artifactory to your JAVA project, please follow these instructions for your specific build system.

For Maven projects, you should add the following repository definition below the repositories tag in your pom.xml

<repositories>
    ...
    <repository>
        <id>maltcms-artifactory-release</id>
        <layout>default</layout>
        <releases>
            <enabled>true</enabled>
        </releases>
        <snapshots>
            <enabled>true</enabled>
            <updatePolicy>daily</updatePolicy>
        </snapshots>
        <url>http://maltcms.de/artifactory/repo</url>
    </repository>
</repositories>

Please note that you can only retrieve artifacts from this repository without authentication that have already been deployed. You can not use the artifactory as a proxy to other repositories.

In order to use the Cross artifacts in your code, include them in the dependencies section of your pom (a):

<dependencies>
    ...
    <dependency>
        <groupId>net.sf.maltcms</groupId>
        <artifactId>cross-test</artifactId>
        <scope>test</scope>
        <version>${1.3.1}</version>
    </dependency>
    <dependency>
        <groupId>net.sf.maltcms</groupId>
        <artifactId>cross-main</artifactId>
        <scope>test</scope>
        <version>${1.3.1}</version>
    </dependency>
</dependencies>

or in the dependency management section of your pom if you want to specify the version explicitly in a multi-module project parent pom (b):

<dependencyManagement>
    <dependencies>
        ...
        <dependency>
        <groupId>net.sf.maltcms</groupId>
        <artifactId>cross-test</artifactId>
        <scope>test</scope>
        <version>1.3.1</version>
    </dependency>
    <dependency>
        <groupId>net.sf.maltcms</groupId>
        <artifactId>cross-main</artifactId>
        <scope>test</scope>
        <version>1.3.1</version>
    </dependency>
    </dependencies>
</dependencyManagement>

With the latter approach, you still need to define the dependencies in your module’s pom like in variant (a), but can omit the <version>...</version> tags.