Thanks for this info. Looking over the Ant build.xml file, I see that
to run the target run-socketserver it needs a log4j-xxx.jar which it
finds in either ~/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar or
in /usr/share/java/log4j-1.2.jar
How does this log4j-xxx.jar get there? I do not see how the POM.xml
gets it to the ~/.m2/repository either.
Can you provide info on where to obtain log4j-<version>.jar from?
thanks,
-Bernie Stumpf
Curt Arnold wrote on 04/02.18:04:
On Mar 31, 2008, at 4:32 PM, Bernard Stumpf wrote:
I've searched for evidence that any of the SocketAppender test cases
were run by the log4cxx tests, and it appears that these tests are
not run. The only related one is "sockethubappendertestcase:
SUCCESS", but that is not a client logger case, I think.
Looking through the log4cxx issues:
LOGCXX-164: XMLSocketAppender is disabled - is marked fixed.
LOGCXX-165 XMLSocketAppender may generate erroneous output - also
marked fixed.
Please explain. Should there be a SocketAppender test case run as
part of the log4cxx tests?
-Bernie Stumpf
Sorry not to get back to you. The test you mention are not run since
they are guarded by an APR_HAS_THREADS, but no APR header files is
included that could potentially set that macro. If you add an
#include "apr.h"
before the
#if defined(APR_HAS_THREADS)
then the test should run (though they don't do much) on every common
platform except Cygwin. I considered, but decided against, trying to
fix that in RC8.
