FYI, I’ve pinged the infra team looking after central about this. I think the issue might be the old metadata in the google-releases repo (which only has the first two releases) is masking the one from releases during aggregation:
https://oss.sonatype.org/content/repositories/google-releases/com/google/inject/guice/maven-metadata.xml vs https://oss.sonatype.org/content/repositories/releases/com/google/inject/guice/maven-metadata.xml If so then it should be straightforward to sort out and will post an update when it’s fixed. -- Cheers, Stuart On Thursday, 16 October 2014 at 19:56, Sam Berlin wrote: > Weird. Per this article > (https://support.sonatype.com/entries/23778606-Why-are-the-latest-and-release-tags-in-maven-metadata-xml-not-being-updated-after-deploying-artifact), > 'latest' seems irrelevant, but 'release' should have been updated when we > deployed the newer versions (if I'm reading it right). > > sam > > On Thu, Oct 16, 2014 at 4:56 AM, Peter Ondruška <[email protected] > (mailto:[email protected])> wrote: > > Hello, can you please update maven metadata to include more recent > > versions, it only has 1.0 and 2.0 > > https://repo1.maven.org/maven2/com/google/inject/guice-parent/maven-metadata.xml -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/9B4D50D6242D4FC9BC09D43BB1B33072%40gmail.com. For more options, visit https://groups.google.com/d/optout.
