... due to a recent upgrade of jboss-metadata to 1.0.0.CR18. The new version exists in the maven repository, but the updated maven-metadata.xml was not checked in.