Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-Id: <6.0.3.0.0.20041209143312.03e9dcd8@mail.qos.ch>
Date: Thu, 09 Dec 2004 14:43:38 +0100
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
From: Ceki =?iso-8859-1?Q?G=FClc=FC?= <ceki@qos.ch>
Subject: Re: cvs commit: logging-log4j/tests build.properties.sample
  build.xml README
In-Reply-To: <20041209055908.59103.qmail@minotaur.apache.org>
References: <20041209055908.59103.qmail@minotaur.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

At 06:59 AM 12/9/2004, mwomack@apache.org wrote:
>mwomack     2004/12/08 21:59:08
>
>   Modified:    tests    build.properties.sample build.xml README
>   Log:
>   Updated files to reflect usage of ./tests/lib directory for external=20
> jars required for test cases.
>   Updated README to explicitly mention the lib dir, what jars are=20
> required, and where to get them.
>   Updated properties to remove the jakarta.oro.jar which can now be=20
> placed in the lib dir instead of a custom property.

Some of the premises outlined above are incorrect. The DB are very
much dependent of the host environment but they are also totally
optional. The only things which was wrong with the test environment as
checked out from CVS was reliance on the existence of tests/lib/
directory. If you just create the tests/lob folder even if its empty
the tests should run smoothly.

I'll make sure that after checking out log4j from CVS and setting
jakarta.oro property, running "ant runAll" works for everyone.


--=20
Ceki G=FClc=FC

  The complete log4j manual:  http://qos.ch/log4j/ =20


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org