Third party JARs

OpenJMS uses third party JARs which maven will automatically attempt to download from a central repository and cache locally.

However, due to licensing restrictions, not all JARs can be automatically downloaded - these need to be done manually. In particular, this applies to JARs distributed by Sun (i.e, the JDBC, JMS, JNDI and JTA JARs).

When maven encounters a JAR it can't download, it will output a message like:

The build cannot continue because of the following unsatisfied dependency:

jdbc-2.0.jar; version override doesn't exist: 2.0 (try downloading from
http://java.sun.com/products/jdbc)

The following table indicates the name of the product, the download archive name, and the path the resulting JAR(s) must be copied to. The JAR(s) may need to be extracted and/or renamed.

In the above, ${maven.repo.local} represents maven's local repository. By default, this is ${user.home}/.maven/repository

Building the OpenJMS JARS

To build all of the OpenJMS JARS:

maven -Dmaven.test.skip o:build
          

NOTE: maven.test.skip prevents the unit tests being run. Need to do this until:

• The http unit tests can be run automatically. These require openjms-tunnel to deployed to a running Tomcat installation.
• A mechanism is set up to only run unit tests if something has changed.

Installing the server

To install the server:

maven -Dmaven.test.skip o:install
          

By default this installs the server to the install/ directory. To override this behaviour, define install.dir in distribution/build.properties

Building a single module

To build a single module, cd to the directory holding the module and run maven from there. E.g, to compile the openjms-net module:

cd modules/net
maven java:compile
          

To install it to the local repository to make it available to other modules:

maven jar:install
          

Building the documentation

To build the website, run:

maven o:site
          

The website will be generated to the target/docs/ directory.