Preparing for samskivert-1.7.4 release.
Preparing for 1.8-SNAPSHOT development.
Support log4j 2.x.

This is an RC dependency. We can update that when log4j 2.0 is release, but that shouldn't be
necessary.
Fix some NPEs and other exceptions in property change handling.

For the 'IntAdjust' and 'BooleanAdjust' classes, handle
PropertyChangeEvents where the values are null or Strings instead of
the expected Integer or Boolean types, respectively.

It's kinda amazing that this has never come up before.
Each Adjust stores to a PrefsConfig, which is backed by a Properties,
which stores all values as Strings. Not only that, but it does not
store in any way what the expected type of a property is.
It is determined by which getter you call:
_cfg.setValue("foo", "2");
_cfg.getValue("foo", (String)null); // returns "2"
_cfg.getValue("foo", 0);            // returns 2
_cfg.getValue("foo", 3.0f);         // returns 2.0f

If a property is removed, then null is the new value, and it also
doesn't know what type the old value was. These runtime adjusts
need to be able to revert to their default value and they will
always need to be able to potentially parse a String. And since
someone can legally change the type of a property, they need
to be able to recover if the property is a type they don't even
expect.

The real problem here is using shitty Properties for backing,
and/or not storing something more complex than the simple toString()
representation of the value.

Don't interpret this fix as a blessing to use these old, old things.
I'm supporting legacy code.

The other adjust subclasses weren't ...adjusted... because my project
doesn't use them and I'm not going to dig in and test them.
Parse booleans like Config does.

Incorrectly.