vmgump recently was moved and in the process we've got log4net to
build mono 1.0 and 2.0 debug builds on Gump (http://vmgump.apache.org/
gump/public/logging-log4net/logging-log4net/gump_work/build_logging-
log4net_logging-log4net.html). From now on out, if you make a code
change that breaks the build, you should receive an automated nag email.
I've been working on migrating the overall Logging Services and log4j
web content to use Maven 2.0 for build and deployment. I expect to
migrate log4cxx over tomorrow. I'd like to take a shot on log4net
thereafter and wanted to give you some advance notice. I'd envision
Maven handling the documentation and packaging and deferring to Nant
actually build the assemblies.
Maven has a standard directory layout (http://maven.apache.org/guides/
introduction/introduction-to-the-standard-directory-layout.html). It
would not be essential to migrate to the standard layout, but it
would make things easier and more consistent with the other
projects. To move to the standard layout:
doc is removed from SVN
examples moves to src/examples
extensions moves to src/extension
src moves to src/main/cs
tests/src moves to src/test/cs
xdocs moves to src/site/xdoc
The layout of examples and extensions seemed pretty complicated, but
don't think it is essential to unwind them. doc can be removed since
Maven would build web content into target/site and site deployment
would commit the generated content into http://svn.apache.org/repos/
asf/logging/site/trunk/doc from which would contain all LS content.
I've made some subsequent changes, but for a preview of Maven see the
web content generated for the last log4j 1.2.15 release candidate at
http://logging.apache.org/log4j/1.2/.
I'd like to move on it to get all of LS consistent. Let me know if
you have any pending commits that would be affected by the change or
any questions or concerns about moving to the standard layout. If
you'd like, I could do the changes on a branch for review.
