Spring was trying to load LDAP-related beans even if no LDAP configuration
had been set, which would result in them throwing exceptions and shutting
everything down.
This marks the beans as @Lazy so they won't get initialized until the first
time they're used, which won't happen if there is no LDAP configuration.
I also went ahead and updated liquibase to 4.4.0 and tested it, and that
seems to work fine, so I'm including that, too.
Spring was trying to load LDAP-related beans even if no LDAP configuration had been set, which would result in them throwing exceptions and shutting everything down.
This marks the beans as @Lazy so they won't get initialized until the first time they're used, which won't happen if there is no LDAP configuration.
I also went ahead and updated liquibase to 4.4.0 and tested it, and that seems to work fine, so I'm including that, too.
Signed-off-by: P. J. Reed phillipreed@hatchbed.com