Previous Topic

Next Topic

Compiling with Ant

Example Ant script files (build-tutorial.xml and build-tutorial.properties in the directory you unzipped the tutorial to) are provided to allow you to compile the resolver and content handler. Make sure that you have Apache Ant installed and set up on your machine first. For more information on installing and running Ant software, read the Apache Ant Manual.

The following structure within the Mulgara installation directory is assumed:

/tutorial
build-tutorial.xml
build-tutorial.properties
/conf
/handler
parserfactory.conf
/handler
/java
compile-handler.list
**Handler package directory structure**
/rdfs
mp3.rdfs
/resolver
/java
compile-resolver.list
**Resolver package directory structure**
/lib
**Supporting jars for the resolver and content handler**

In This Section

See Also

HTTP Resolver and MP3 Content Handler Tutorial

Prerequisites

Developing Protocol Resolvers

Developing Content Handlers

Integrating into Mulgara

Change the following properties:

  • server-version property in the build-tutorial.properties file to be the version of the server you are using. For example, 1.1.0
  • server.base.dir property to the directory you installed TKS in

All other properties should not require changing.

Both of the modules used in this tutorial are in the Mulgara distribution and can be built using the main build file.

From the main directory of your Mulgara installation, run:

  • build.bat content-mp3-jar (for systems running a Linux® or UNIX® operating system use ./build.sh content-mp3-jar)

    This produces the file content-mp3-base-<Mulgara version>.jar (where <Mulgara version> is the version of your Mulgara installation) in the bin directory.

  • build.bat resolver-http-jar (for systems running a Linux® or UNIX® operating system use ./build.sh resolver-http-jar)

    This produces a file called resolver-http-base-<Mulgara version>.jar in the bin directory.

Open Source logo

© 2001-2004 Tucana Technologies, Inc. Some rights reserved.

© 2006 The Mulgara Project. Some rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".