Oh man, this is awesome.

Everything looks OK here, nothing has blown up as far as I can tell. Did a quick run of it, made sure OpenNMS still runs as a smoke test. I say ship it!

I did a squash-merge and committed it under your authorship, DJ:

commit 4d25ef1e7cc2f430e5b5fadfdde5dfae5c517839
Author: DJ Gregor <dj@opennms.org>
Date: Fri Mar 11 12:51:51 2011 -0500

configuration test tool

This creates a new script in $OPENNMS_HOME/bin
called "config-tester" which will use Spring to check
that every configuration file is valid and can be
loaded.

$ config-tester -h
usage: config-tester -a
OR: config-tester [config files]
OR: config-tester -l
OR: config-tester -h
a,-all check all supported configuration files
h,-help print this help and exit
l,-list list supported configuration files and exit
v,-verbose list each configuration file as it is tested

Given how much stuff this messes with (moving classes from webapp and such into dao) I'm going to say it should not go back into 1.8, but I'm up for merging it into 1.9. Seems reasonable otherwise.

I'll do some quick testing and then merge it.

I was going to look at integrating this, but can you explain why you got rid of the spring-security-core dependency?

Oop, I see. You got rid of the duplicate dependency, but at some point, so did we, so now we have no dependency at all.

I'll put it back.

I just committed a few additional changes in commit 333c613e2a0ee40c04f3cce22771fbc3a9410064. This should be ready to go. What needs to be done to move it into master? It also should be back-portable to 1.8 pretty easily, if that's desirable--I purposefully tried to make no code changes outside of this Maven project.