Fixed unassociate and respective test units

[LadislavSopko]

Hello,

I made all unassiciate and unsetContent functions with the same logic for all stores.
Added also respective TestUnits.

Regards
ladislav

[coveralls]

Coverage increased (+0.5%) to 81.504% when pulling 5ba70ad on LadislavSopko:feature/ladislav/adjustmongostore into 23ee7b1 on paulcwarren:wip/springboot2.

[LadislavSopko]

Codacy is still there,
and detect wrongly static imports, and duplicated code in test units
which must be the same, if test the same on different implementations .....
It can be surely good service, but maybe it should not check tests?

[paulcwarren]

OK. I removed the project from codacy itself. The quality review is still there but if you try details it now produces an error so perhaps...maybe...it will now be gone!

[paulcwarren]

Does your first commit switch back to <plugins> and then the second switch back again to <pluginsManagement>?

If you are having issues with that in eclipse and the "Plugin execution not covered by lifecycle configuration" issue. It's because m2eclipse doesn't know about the asciidoc maven plugin and how or whether to configure it into the incremental build. You don't want to configure it into the incremental build. There are a couple of ways to ignore it. Usually I choose the quickfix that sets it to ignore in your workspace settings.

[LadislavSopko]

I removed <pluginsManagement> and setup eclipse wsp to ignore it.

[LadislavSopko]

LOL,
Codacy popped UP again ?