Fix broken maven-metadata.xml through Nexus

January 17, 2009 – 21:41 | java | Tags: , , ,

The log4j maven-metadata.xml hosted at ibiblio is missing the latest two versions, 1.1.14 and 1.1.15. It becomes a problem for me as an Ivy user, too, since Ivy 2.0 adds the ability to use maven metadata to list available versions.

Fortunately I have a Nexus repository as the aggregator/proxy to all the external repositories. Brian from the Nexus IRC room pointed me to this solution/workaround: add the fixed maven-metadata.xml to a repo hosted by Nexus – e.g., the “3rd Party” repo coming out of box in Nexus. Then create a group to aggregate the 3rd Party and the public Ibiblio repos. The “virtual” group repo will automatically create a merged maven-metadata.xml on the fly whenever it is requested.

And it works like a charm. Thanks, Brian!

Trackback from your site, or follow the comments in RSS.
  1. 2 Responses to “Fix broken maven-metadata.xml through Nexus”

  2. You’re welcome. Since you’re using nexus with ivy, if you have ideas about how nexus can provide any better support for ivy users, we’d love to hear them.

    By Brian Fox on Jan 18, 2009

  3. You can easily achieve the same result with Artifactory, BTW, using virtual repositories, which will do metadata aggregation on the fly with the local ones. You can just upload the right pom/jar version (so no need to fix the metadata by hand) and the metadata of your local repository will be updated to include the right version.

    By Yoav Landman on Jan 18, 2009

Post a Comment