question-mark
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.

Semver can't be resolved because Semver pom.xml is missing from JFrog

See original GitHub issue

If your root build is just this:

plugins {
    id("org.jlleitschuh.gradle.ktlint-idea") version "6.2.1"
}

You get the following exception:

./gradlew tasks

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'root-dependency-manager'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find net.swiftzer.semver:semver:1.1.0.
     Searched in the following locations:
       - file:/Users/jonathanleitschuh/.gradle/caches/5.0-rc-1/embedded-kotlin-repo-1.3.0-2/repo/net/swiftzer/semver/semver/1.1.0/semver-1.1.0.jar
       - https://plugins.gradle.org/m2/net/swiftzer/semver/semver/1.1.0/semver-1.1.0.pom
     Required by:
         project : > org.jlleitschuh.gradle.ktlint-idea:org.jlleitschuh.gradle.ktlint-idea.gradle.plugin:6.2.1 > gradle.plugin.org.jlleitschuh.gradle:ktlint-gradle:6.2.1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

This is because the semver plugin isn’t published to the Gradle plugin portal. We should consider embedding that project’s one source file in our build as a vendored dependency.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
Tapchicomacommented, Dec 9, 2018

@fractalwrench note that due to Gradle plugin portal changes, plugin id changed, if you are using classpath approach:

classpath "org.jlleitschuh.gradle:ktlint-gradle:6.3.1"
1reaction
Tapchicomacommented, Nov 26, 2018
Read more comments on GitHub >

github_iconTop Results From Across the Web

NuGet Repositories - JFrog - JFrog Documentation
Debugging NuGet packages directly using Artifactory as Your Symbol Server_doc; Support for NuGet API v3 Registries. Support for NuGet SemVer 2.0 ...
Read more >
Artifactory Release Notes - JFrog
Overview. This page presents release notes for JFrog Artifactory describing the main fixes and enhancements made to each version as it is released....
Read more >
Release Notes - Artifactory 6.x - JFrog Wiki
Overview. This page presents release notes for JFrog Artifactory describing the main fixes and enhancements made to each version as it is released....
Read more >
How To Troubleshooting Artifactory 7.x Upgrade Issues - JFrog
Resolution : This behavior usually occurs when upgrading an HA node as a standalone Artifactory instance. You can identify your Artifactory type ...
Read more >
Error while deploying a jar that contains a pom.xml ... - JFrog
How did you deploy it? If you used the deploy plugin and it failed then it's a bug. If you used the UI...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found