comparison 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
comparison
equal deleted inserted replaced
123:ddbb7256246f 124:7261c948425c
1 ============
2 DEPENDENCIES
3 ============
4
5 - JUnit 3.8.1
6 - Log4j 1.2.14
7 - Restlet 2.0-SNAPSHOT
8 - Restlet-XML 2.0-SNAPSHOT
9
10
11 ============================ 1 ============================
12 COMPILATION AND INSTALLATION 2 COMPILATION AND INSTALLATION
13 ============================ 3 ============================
14 4
15 This project is based on maven2. To compile/install this client, just do: 5 This project is based on Maven. To compile/install this client, just do:
16 6
17 mvn compile package 7 mvn compile package
18 8
19 The result will be an jar-archive in the ``target`` directory. 9 The result will be an jar-archive in the ``target`` directory.
20 10
39 29
40 ================== 30 ==================
41 RUNNING THE CLIENT 31 RUNNING THE CLIENT
42 ================== 32 ==================
43 33
44 There is a bash script in the ``contrib`` directory. This might be used to 34 There is a bash script that might be used to
45 start the console based client. Note, that you need the jars of the depending 35 start the console based client. Note, that you need the jars of the depending
46 libraries in the ``target`` directory. 36 libraries in the ``target`` directory.
47 37
48 sh bin/run.sh 38 sh bin/run.sh
49 39

http://dive4elements.wald.intevation.org