Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

io.buoyant:admin-names_2.12:jar:1.4.1 not available on Maven central

See original GitHub issue

Issue Type:

Bug report
Feature request

What happened:

It looks like the new module io.buoyant:admin-names_2.12:jar:1.4.1 didn’t make it to Maven central.

What you expected to happen:

It should be there

How to reproduce it (as minimally and precisely as possible):

Create a maven project with this content in the pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>test</groupId>
  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>

  <dependencies>
    <dependency>
      <groupId>io.buoyant</groupId>
      <artifactId>linkerd-main_2.12</artifactId>
      <version>1.4.1</version>
    </dependency>
  </dependencies>
</project>

Then run mvn dependency:tree:

> mvn dependency:tree
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------------------------< test:test >------------------------------
[INFO] Building test 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for io.buoyant:admin-names_2.12:jar:1.4.1 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.132 s
[INFO] Finished at: 2018-05-28T11:45:15+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project test: Could not resolve dependencies for project test:test:jar:1.0-SNAPSHOT: Failure to find io.buoyant:admin-names_2.12:jar:1.4.1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExceptio

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

2reactions

adleongcommented, May 29, 2018

Thanks for reporting! I think I see how this artifact got missed… I’ll get it uploaded asap.

0reactions

robertpanzercommented, May 30, 2018

Thanks! I just retrieved the artifact from Maven central.

Top Results From Across the Web

Maven Central Repository Search

Official search by the maintainers of Maven Central Repository. ... Introducing the new look of The Central Repository, designed to address artifact search ......

Maven – Guide to uploading artifacts to the Central Repository

Guide to uploading artifacts to the Central Repository. In order for users of Maven to utilize artifacts produced by your project, you must...

Upgrade Android Project from JCenter to Maven Central

Follow these steps to add Maven Central to your project to continue getting Android SDK updates.

Maven Could not resolve dependencies, artifacts could not be ...

The jar file , jar_file_name , group_id , artifact_id and version_no are available from the maven repository page. Share.

Where is Maven Central Repository? - Mkyong.com

By default, Maven will get project dependencies from Maven Local Repository, if it is not found, Maven will get it from the Maven...