view README @ 124:7261c948425c 3.2.x

Rely on log4j's default initialization procedure This should make upgrading to Log4j 2.x easier. In passing, use latest Log4j 1.
author Tom Gottfried <tom@intevation.de>
date Fri, 25 Feb 2022 15:15:04 +0100
parents a1db30b33f43
children
line wrap: on
line source
============================
COMPILATION AND INSTALLATION
============================

This project is based on Maven. To compile/install this client, just do:

    mvn compile package

The result will be an jar-archive in the ``target`` directory.

If you want to use the contrib script ``run.sh`` (see below), you will need
the jars of the dependencies as well. Therefore, just do:

    mvn compile package dependency:copy-dependencies

This command will compile the sources, build a jar of those and download the
depending jar archives to ``target/dependency``.


=============
CONFIGURATION
=============

Currently, this client reads two configuration files:

    - the artifact configuration (conf/demo-config.conf)
    - the logging configuration (conf/log4j.properties)


==================
RUNNING THE CLIENT
==================

There is a bash script that might be used to
start the console based client. Note, that you need the jars of the depending
libraries in the ``target`` directory.

    sh bin/run.sh

http://dive4elements.wald.intevation.org