It would have probably been a good thing to check if PluginTestCase
was actually run in log4j 1.3 before I added it to the components
project. It wasn't (due to the override of the suite() method) and
once I tried running the tests they also failed on log4j 1.3. I
hacked the test suite so all tests pass on log4j 1.3 and then moved
it over the components project. Other than the means of getting a
PluginRegistry and a final log4j internal log message going to the
console instead of the log file, the tests are the same and pass in
both environments.
I've been playing around with the site generation and about ready to
replicate it on the other companion projects. There are a few
oddities that I think I'll need to ask for help on one of the Maven
mailing lists. The oddities I've seen:
An XML parsing error on the test report when running Maven 2.0.6
which doesn't occur on Maven 2.0.4.
Duplicate entries in the menu for the Surefire test report.
A false report of 100% coverage from the coverage analysis. This is
a known error that occurs in version 2.1 of the plugin, so the
pom.xml specifies that version 2.0 should be used. However, using
2.0 doesn't reliably produce a valid report. It seems to work better
if you delete any stray surefire* files from the base directory and
after removing ~/.m2/repository/org/codehaus/mojo/cobertura-maven-
plugin.
I've added a minimal build.xml file for the project and added a Gump
descriptor, so we should have a Gump building this shortly (the nags
go to me personally until things are checked out).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
