Update Maven with version 3

[Peter Ondruška]

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

[Sam Berlin]

Weird.  Per this article, '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 <peter.o...@gmail.com> 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 google-guice...@googlegroups.com.
To post to this group, send email to google...@googlegroups.com.
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/ec19ca80-67b7-481e-90c9-735dfc1f2b09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stuart McCulloch]

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

[Sam Berlin]

Thanks, Stuart!

--
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 google-guice...@googlegroups.com.
To post to this group, send email to google...@googlegroups.com.
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.

[Stuart McCulloch]

No worries, the metadata has been updated

[Sam Berlin]

Out of curiosity, what are the implications of fixing it? 

sam

--
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 google-guice...@googlegroups.com.
To post to this group, send email to google...@googlegroups.com.
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/A6BFE07E34AA4558AA9DB801F272F192%40gmail.com.

[Stuart McCulloch]

On Friday, 17 October 2014 at 23:31, Sam Berlin wrote:

Out of curiosity, what are the implications of fixing it? 

Some plugins like the versions-maven-plugin use it to check for and display updates. It’s also used when people have LATEST or RELEASE as meta-versions in their pom.xml though that’s discouraged these days because it leads to non-reproducible builds. IDEs typically use the separate Maven index (based on lucene) for general searching of artifacts as it’s more flexible.

[Peter Ondruška]

Great, thanks :)