You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by mw...@apache.org on 2004/12/09 06:59:08 UTC
cvs commit: logging-log4j/tests build.properties.sample build.xml README
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 jars required for test cases.
Updated README to explicitly mention the lib dir, what jars are required, and where to get them.
Updated properties to remove the jakarta.oro.jar which can now be placed in the lib dir instead of a custom property.
Revision Changes Path
1.7 +2 -28 logging-log4j/tests/build.properties.sample
Index: build.properties.sample
===================================================================
RCS file: /home/cvs/logging-log4j/tests/build.properties.sample,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.properties.sample 11 Jun 2004 19:43:03 -0000 1.6
+++ build.properties.sample 9 Dec 2004 05:59:08 -0000 1.7
@@ -1,30 +1,4 @@
deprecation=on
-jakarta.oro.jar=../../jakarta-oro-2.0.5/jakarta-oro-2.0.5.jar
-
-
-# Junit test cases
-# ================
-# junit.jar must be on the classpath or in ANT_HOME/lib. It can't be
-# handled as a property altough this might change in futute versions of ANT.
-
-# We use jetty for some unit tests
-jetty.jar=/java/jetty-4.2.20/lib/org.mortbay.jetty.jar
-
-
-# Database testing
-# ================
-#
-# For the various DB tests you need to place the appropriate
-# JDBC drivers in ./tests/lib/ directory.
-#
-# Testing JNDIConnectionSource requires JNDI File System Service
-# Provider, 1.2 Beta 3, which can be downloaded from:
-#
-# http://java.sun.com/products/jndi/downloads/index.html
-#
-# Click on "Download JNDI 1.2.1 & More"
-#
-# Once you obtained the JNDI File System Service Provider place
-# the files fscontext.jar and providerutil.jar in the ./tests/lib/
-# directory.
\ No newline at end of file
+# normally other build related properties would be defined here, but for now
+# there are no other required properties.
\ No newline at end of file
1.69 +0 -1 logging-log4j/tests/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/logging-log4j/tests/build.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- build.xml 8 Dec 2004 20:23:34 -0000 1.68
+++ build.xml 9 Dec 2004 05:59:08 -0000 1.69
@@ -30,7 +30,6 @@
<pathelement location="${tests.source.home}"/>
<pathelement location="./classes"/>
<pathelement location="./resources"/>
- <pathelement location="${jakarta.oro.jar}"/>
<fileset dir="./lib/">
<include name="*.jar"/>
</fileset>
1.9 +24 -5 logging-log4j/tests/README
Index: README
===================================================================
RCS file: /home/cvs/logging-log4j/tests/README,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- README 9 May 2002 08:32:53 -0000 1.8
+++ README 9 Dec 2004 05:59:08 -0000 1.9
@@ -20,11 +20,30 @@
IMPORTANT: You need to place junit.jar in your CLASSPATH environment
variable.
-The test cases perform some regular expression based filtering. This
-requires jakarta-oro. Version-2.0.5 was used when writing the
-tests. You need to have jakarta.oro.jar property (found in the
-build.properties file) to point to jakarta-oro.jar. See the file
-build.properties.sample for an example of a build.properties file.
+====================
+
+The test cases are also dependent on other external projects and jars.
+The following jars should be placed in the ./tests/lib directory:
+
+jakarta-oro - http://jakarta.apache.org/oro - The test cases perform some
+regular expression based filtering. Version-2.0.5 was used when writing the
+tests, but later versions should be compatible.
+
+jetty - http://jetty.mortbay.org/jetty/ - Version 4.2.22 was used when writing
+the tests. You will need both the org.mortbay.jetty.jar and the
+org.mortbay.jetty.plus.jar
+
+Optional database testing - For the various DB tests you need to place the
+appropriate JDBC drivers in ./tests/lib/ directory.
+
+Optional JNDI related testing - Testing JNDIConnectionSource requires
+JNDI File System Service Provider, 1.2 Beta 3, which can be downloaded from:
+http://java.sun.com/products/jndi/downloads/index.html. Click on
+"Download JNDI 1.2.1 & More". Once you obtained the JNDI File System Service
+provider place the files fscontext.jar and providerutil.jar in the ./tests/lib/
+directory.
+
+====================
Assuming jakarta-ant is installed properly, depending on your platform
type $ANT_HOME/bin/ant or %ANT_HOME%/bin/ant.bat to see the available
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: cvs commit: logging-log4j/tests build.properties.sample
build.xml README
Posted by Ceki Gülcü <ce...@qos.ch>.
Contrary to what I stated perviously, the jetty jar files are indeed
necessary to compile the PassByJNDI class. Work is in progress to make
this class optional.
At 02:43 PM 12/9/2004, Ceki Gülcü wrote:
>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.
>
>
>--
>Ceki Gülcü
>
> The complete log4j manual: http://qos.ch/log4j/
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: cvs commit: logging-log4j/tests build.properties.sample
build.xml README
Posted by Ceki Gülcü <ce...@qos.ch>.
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
> jars required for test cases.
> Updated README to explicitly mention the lib dir, what jars are
> required, and where to get them.
> Updated properties to remove the jakarta.oro.jar which can now be
> 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.
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org