Skip to end of metadata
Go to start of metadata

XFire maintains two build systems side by side: Maven and Ant. Both can be used for testing and buliding jars. Maven is used for building releases and distributions. A couple notes on how our build system is set up:

In the xfire directory, there are several different modules. These can be compiled individually or as an aggregate, named "xfire-all". The xfire-all module is solely used in the maven build to build an aggregate xfire-all jar. The ant build system does not require this.

Building with Ant

Building individual jars

To compile jars for all the modules run

from the main directory. This will put a jar in each module's target directory. For example, the xfire-core jar will be placed in xfire-core/target as "xfire-core-VERSION.jar".

Building an "xfire-all" jar

To compile an jar of all the xfire modules run

from the main directory. The resultant jar will be placed in xfire/target.

Running Tests

To run tests for all modules run

from the main directory.

To run tests for an individual module:

Building with Maven

To build with java 5.0 support you must included "-Dxfire.java5=true" in all your maven commands.

Building all the individual jars

To build jars for each xfire module and have them placed in your local maven repository, simply run "maven" from the main source directory.

Building an individual module

To build an individual module:

Building an "xfire-all" jar

or if you desire java 5.0 support:

Additional notes

 - due to license problems you may need to install some jars manualy in your local repo. Like :
xmlbeans-jsr173-api from 

- xfire-jibx module MUST be build with tests enabled ( if you turn test off with -Dmaven.test.skip  then build will fail ).

  • No labels