RepositoryRegistry is used for indexing context now. There is still more work to do
to move the maven dependent parts into its own projects and update the dependencies.

Not finished yet, but uses the maven index service via spring dependency injection
Moving some maven specific classes to subpackages

Combining the indexer api and repository api into archiva-repository-api
They have bidirectional dependencies so they are put together in one module.

Adding new classes for a generalized indexer api that will be used for interfaces
and implementation independent tasks.

Adding content provider service that creates repository content instances
remove direct access to the repository content instances.

Using the repository api and RepositoryRegistry for repo access

As suggested in the SLF4J FAQ:
https://www.slf4j.org/faq.html#logging_performance
.. parameterized logging can improve the efficiency of logger calls when
logging at the specified level is disabled.

In addition, per the FAQ: https://www.slf4j.org/faq.html#paramException
since SLF4J 1.6.0 it is possible to use parameterized logging and also
log an exception/throwable.

toString() is called automatically:
https://www.slf4j.org/faq.html#string_contents

These changes were suggested by SLF4J Helper for NetBeans IDE:
http://plugins.netbeans.org/plugin/72557/

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

Remove the JDO dependencies and set the JPA implementation as only
database alternative and default implementation. Uses the same database
as JDO before.

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

create a copy to avoid ConcurrentModificationException