repository

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

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/

The column 'key' can't be queried in Cassandra

Probably because 'key' is reserved for the element key or a limitation in Hector

Some caveats with Cassandra implementation:

We can't search artifacts by any (wildcard) property, so searchArtifacts(text,...) just calls getArtifactsByMetadata

The exact parameter is ignored as we can't do non exact searches in Cassandra

Added REST methods:

artifactsByProjectVersionMetadata/{key}/{value}

artifactsByMetadata/{key}/{value}

artifactsByProperty/{key}/{value}

searchArtifacts/{text}

searchArtifacts/{key}/{text}

In JCR implementation When searching into any property (key = nil) we can't do exact searchs