@ConditionalOnMissingBean on javers(connectionProvider) for Mongo and Sql

[abibell]

Fix for http://stackoverflow.com/questions/39322714/javerssqlautoconfiguration-javers-not-getting-called

[bartoszwalacik]

@abibell I thought that this PR is about adding @ConditionalOnMissingBean to javers starters configuration. Then you could replace default javers bean with your javers bean with your configuration (scanTypeName()).
We didnt talked abould implementing scanTypeNames(). This is another issue - #263
And I think that javers should use some dedicated lib for classpath scanning.

[bartoszwalacik]

The first commit in this PR is OK, the second is not OK. I will merge if you remove the second commit. I think, the first one is enough to solve your issue

[abibell]

Oops, 2nd commit wasn't meant to come into PR. Try it now.

With regards to second issue, what would library do you have in mind to use, is it worth it? Do you see introducing the classpath scanning library can be a separate issue to getting scanTypeNames(package)?

[bartoszwalacik]

yes, there is a separate issue for that - #263
Some research is needed, the ann scanning lib should be small (no dependencies) and fast

[bartoszwalacik]

released in 2.2.2