In both Infinispan and Hibernate we define a main logger in the core project, and extend this in each other module. In practice it looks like:

@MessageLogger(projectCode = "ISPN")
public interface Log extends BasicLogger {

   @LogMessage(level = WARN)
   @Message(value = "Field %s not found!!", id = 2)
   void fieldNotFound(String fieldName);

...

@MessageLogger(projectCode = "ISPN")
public interface Log extends org.infinispan.util.logging.Log {

   @LogMessage(level = ERROR)
   @Message(value = "Could not locate key class %s", id = 14001)
   void keyClassNotFound(String keyClassName, @Cause Exception e);

...

since the last release 1.0.0.CR3 all extending modules fail to build with the following error message:

[INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message.
[INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message.
[INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message.
[INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message.
[many more..]

So we had to rollback this dependency upgrade and stick with older versions.

See also
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/268/org.infinispan$infinispan-query/console
caused by
https://github.com/infinispan/infinispan/blob/master/query/src/main/java/org/infinispan/query/logging/Log.java