18 Packaging Kauri applications

While developing a Kauri application, you will typically launch Kauri from the command line. Kauri will by default use the conf directory in the current directory, and retrieve all needed artifacts from your local Maven repository. Because of this, no special packaging is needed to run an application during development, reducing the build-run cycle.

However, at some point, you will have to package your application to distribute it to the users or to put it on some server for deployment.

A packaged Kauri application consists minimally of:

• a configuration directory (containing at least the wiring.xml file)
• a repository containing all the artifacts (jars) used by the project: your own used modules, reused Kauri modules, and their dependencies

Besides that, it can also include logging configuration, application configuration, Java service wrapper configuration, documentation, and any other resources needed by your application.

There are basically two approaches:

• Packaged Kauri application
• Servlet webapp

18.1 Packaged Kauri application

18.1.1 What it is

A packaged Kauri application consists of a directory containing everything to run your application, except for Kauri itself.

It has no new concepts or features of its own, it is just a standard method for packaging a Kauri application.

[todo: still needs work: The directory can also contain documentation, installation scripts, and any other resources needed by your application]

A packaged Kauri application can be created by means of the Maven plugin kauri-package-plugin.