the version was already bumped to 2.4 for lift-mongodb, but not for lift-mongodb-record.
there's also a fix to apply the WriteConcern on a save to that operation only. currently, WriteConcern.STRICT would be set for the whole collection for some period of time and if there were an error, would never be set back.

the new driver is more proactive about establishing a connection at construction time, so I had to make the construction lazy to work with the unit tests.
there was also a problem where the MongoAddress and MongoHost were concrete classes with vals that could not be overridden.