[1.9.x] Name mappers cleanup and new GAECV mapper

[cstamas]

Cleanup name mappers usage and introduce new, more selective mapper GAECV.

Changes:

• introduce GAECV next to existing GAV name mapper.
• make default GAECV

[gnodet]

Missing @since

[cstamas]

fixed

[gnodet]

Cleanup name mappers usage and introduce new, more selective mapper GAECV.

Changes:

• introduce GAECV next to existing GAV name mapper.
• make default GAECV

So we're diminishing lock contentions at the cost of acquiring more locks, right ?

[cstamas]

So we're diminishing lock contentions at the cost of acquiring more locks, right ?

Yes, client code of SyncContext still asks for same number of artifacts/metadata, but existing GAV name mapper coalesced them into GAV-only. But IMO it is worth it (unless we see something down the road; but then we just need to swap back the default one in adapter), as so far we locked "whole GAV" even if some classifier was needed only, hurting badly concurrency.