Error Retrieving Pom Of Module Dependency
Contents |
v4.0.0 POMAgile Board ExportXMLWordPrintableJSON Details Type: Bug Status: Closed Priority: Major Resolution: unresolved dependency: org.scala-sbt#sbt;0.13.7: not found Fixed Affects Version/s: 2.0.1 Fix Version/s: 2.2-beta-2 Component/s: unresolved dependency: org.scala-sbt#sbt;0.13.9: not found None Labels: None Environment: Linux Unbuntu, 1.5_07 jdk Description I have a
Error During Sbt Execution: Error Retrieving Required Libraries
maven 1 project that builds a jar file called pps-3.0.2.jar. The jar (and it's pom) are moved into my legacy
Unresolved Dependency: Org.scala-sbt#sbt;0.13.11: Not Found
style repository. I have a maven 2 project that depends on pps-3.0.2. It compiles and tests the code fine. During the assembly it is suppose to creates a directory of dependent jar files and it blows up with the message: org.scala-sbt#sbt 0.13.8 not found ---------------------------------------------------------------------- Error building POM (may not be this project's POM). Project ID: ebs:pps POM Location: /home/chelck/.m2/repository/ebs/pps/3.0.2/pps-3.0.2.pom Reason: Not a v4.0.0 POM. ------------------------------------------------------------------------- In a sense the error is correct: pps-3.0.2.pom is not v4.0.0 - it's legacy. So why is mvn trying to build it's POM and why doesn't it realize it's a legacy pom? I see this with maven 2.0.4,2.0.6, and 2.0.7. Here is a (2.0.4) stack trace: [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher
here
Unresolved Dependency: Org.scala-sbt#sbt;0.13.8: Not Found
for a quick overview of the site error could not retrieve sbt 0.13 7 Help Center Detailed answers to any questions you might have Meta Discuss sbt unresolved dependency not found the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more https://issues.apache.org/jira/browse/MASSEMBLY-225 about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each http://stackoverflow.com/questions/19805102/unresolved-dependency-org-scala-sbtsbt0-13-not-found-when-running-sbt-0-13 other. Join them; it only takes a minute: Sign up Unresolved dependency: org.scala-sbt#sbt;0.13: not found when running sbt 0.13? up vote 7 down vote favorite 1 I have a Scala project consisting of a few ones. I decided to start using sbt 0.13. Here is ~/sbt/repositories: [repositories] local sbt-releases-repo: http://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] sbt-plugins-repo: http://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] maven-central: http://repo1.maven.org/maven2/ But still I get an error: Getting org.scala-sbt sbt 0.13 ... :: problems summary :: :::: WARNINGS module not found: org.scala-sbt#sbt;0.13 ==== local: tried /home/alex/.ivy2/local/org.scala-sbt/sbt/0.13/ivys/ivy.xml ==== sbt-releases-repo: tried http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13/ivys/ivy.xml ==== sbt-plugins-repo: tried http://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.scala-sbt/sbt/0.13/ivys/ivy.xml ==== maven-central: tried http://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13/sbt-0.13.pom :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.scala-sbt#sbt;0.13: not found :::::::::::::::::::::::::::::::::::::::::::::: :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS unresolve
here for a quick overview of the site Help Center Detailed answers http://stackoverflow.com/questions/18505176/unresolved-dependency-sbt-0-13-0-after-update to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business https://docs.gradle.org/current/userguide/dependency_management.html Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack not found Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Unresolved dependency SBT 0.13.0 after update up vote 10 down vote favorite 6 Please have a look on the comments to be up to date. error retrieving pom Update SBT to 0.13.0: I have a couple of projects written with scala 2.10.2 and build with sbt 0.12.4. As my OS is Ubuntu I used the SBT.deb package for installation of sbt 0.12.4. Everything fine. I built my projects with sbt. Yesterday I wanted to update sbt to version 0.13.0. I downloaded and installed the new .deb package. The projects configuration has not been changed. The failure: When runnging SBT after the update I get this failure: $ sbt Loading /usr/share/sbt/bin/sbt-launch-lib.bash Getting org.scala-sbt sbt 0.13.0 ... :: problems summary :: :::: WARNINGS module not found: org.scala-sbt#sbt;0.13.0 ==== local: tried /home/myUser/.ivy2/local/org.scala-sbt/sbt/0.13.0/ivys/ivy.xml :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.scala-sbt#sbt;0.13.0: not found :::::::::::::::::::::::::::::::::::::::::::::: :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS unresolved dependency: org.scala-sbt#sbt;0.13.0: not found Error during sbt execution: Error retrieving required libraries (see /home/myUser/.sbt/boot/update.log for complete log) Error: Could not retrieve sbt 0.13.0 The ~/.sbt/update.log
How dependency resolution works24.8. Fine-tuning the dependency resolution process24.9. The dependency cache24.10. Strategies for transitive dependency management24.1.IntroductionDependency management is a critical feature of every build, and Gradle has placed an emphasis on offering first-class dependency management that is both easy to understand and compatible with a wide variety of approaches. If you are familiar with the approach used by either Maven or Ivy you will be delighted to learn that Gradle is fully compatible with both approaches in addition to being flexible enough to support fully-customized approaches. Here are the major highlights of Gradle's support for dependency management:Transitive dependency management: Gradle gives you full control of your project's dependency tree. Support for non-managed dependencies: If your dependencies are simply files in version control or a shared drive, Gradle provides powerful functionality to support this. Support for custom dependency definitions.: Gradle's Module Dependencies give you the ability to describe the dependency hierarchy in the build script. A fully customizable approach to Dependency Resolution: Gradle provides you with the ability to customize resolution rules making dependency substitution easy. Full Compatibility with Maven and Ivy: If you have defined dependencies in a Maven POM or an Ivy file, Gradle provides seamless integration with a range of popular build tools. Integration with existing dependency management infrastructure: Gradle is compatible with both Maven and Ivy repositories. If you use Archiva, Nexus, or Artifactory, Gradle is 100% compatible with all repository formats. With hundreds of thousands of interdependent open source components each with a range of versions and incompatibilities, dependency management has a habit of causing problems as builds grow in complexity. When a build's dependency tree becomes unwieldy, your build tool shouldn't force you to adopt a single, infle