On Apr 28, 2007, at 4:32 PM, Paul Smith wrote:
On 28/04/2007, at 10:16 PM, Curt Arnold wrote:
Did you svn update, rebuild and install log4j 1.2.15? The
fragment of DTD that shines through in the warnings is prior to
the recent changes to log4j 1.2.15.
Definitely, several times.
I found a bug in component, but I don't think it affected you. Also
the Ant build was out of sync. I'm thinking the likely culprit is an
Maven built log4j 1.2.15 triggering chaos due to a missing log4j.dtd
resource.
My suggestions:
a) If you built log4j 1.2.15 with Maven, remove it from the
repository, build it with Ant and install it using mvn
install:install-file (attempt to build the bridge and it will tell
you the syntax). The Maven build doesn't include the log4j.dtd,
LICENSE, NOTICE and other resources that the Ant build places in the
Jar.
b) svn update component and mvn install
c) Try to run the tests again on a fresh checkout. If the test fails
under Maven, try the ant build.
If eclipse and ant pass and maven fails, then we should take take it
to [EMAIL PROTECTED] I would suggest before doing that downloading and
installing a Gump built log4j 1.2.15 and trying the process again.
It would make it easier for any Maven guru debugging the issue to not
have to learn how to build log4j.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
