I upgraded sbt from version 0.13.8 to 0.13.9. We have Nexus proxying many repositories. Now, when I issue 'sbt' command - I get unresolved dependencies
scala-library
scala-compilre
scala-reflect
all due to sha1 different from the computed. Is there a way to bypass sha1 validation?
FYI. setting checksums in update := Nil in build.sbt does not solve the problem. I even tried putting
<property name="ivy.checksums" value=""/> in ~/.ivy/ivysettings.xml still fails.
here is the console output:
D:\Temp\test>sbt -v update
Getting org.scala-sbt sbt 0.13.9 ...
:: problems summary ::
:::: WARNINGS
problem while downloading module descriptor: http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-library/2.10.5/scala-library-2.10.5.pom: invalid sha1: expected=c39e31e37ce77d8d5fb8e8c640222275815d36f2 computed=4e8b721680f2defb491fe90447302658d464d5c
0 (351ms)
module not found: org.scala-lang#scala-library;2.10.5
==== local: tried
C:\Users\ak\.ivy2\local\org.scala-lang\scala-library\2.10.5\ivys\ivy.xml
-- artifact org.scala-lang#scala-library;2.10.5!scala-library.jar:
C:\Users\ak\.ivy2\local\org.scala-lang\scala-library\2.10.5\jars\scala-library.jar
==== my-ivy-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/ivy-releases/org.scala-lang/scala-library/2.10.5/ivys/ivy.xml
==== my-maven-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-library/2.10.5/scala-library-2.10.5.pom
problem while downloading module descriptor: http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-compiler/2.10.5/scala-compiler-2.10.5.pom: invalid sha1: expected=9a85822af1f9ea46b49dfdfa99eafc0bd819abaf computed=c3e0b6cf2f45a5a7cb052ef9e00f8fdac55e7
1b7 (69ms)
module not found: org.scala-lang#scala-compiler;2.10.5
==== local: tried
C:\Users\ak\.ivy2\local\org.scala-lang\scala-compiler\2.10.5\ivys\ivy.xml
-- artifact org.scala-lang#scala-compiler;2.10.5!scala-compiler.jar:
C:\Users\ak\.ivy2\local\org.scala-lang\scala-compiler\2.10.5\jars\scala-compiler.jar
==== my-ivy-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/ivy-releases/org.scala-lang/scala-compiler/2.10.5/ivys/ivy.xml
==== my-maven-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-compiler/2.10.5/scala-compiler-2.10.5.pom
problem while downloading module descriptor: http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-reflect/2.10.5/scala-reflect-2.10.5.pom: invalid sha1: expected=3a6fa11041ac0c8b4d5fcf9d4f1372ba8c0b7216 computed=30f1f646114a79eeefb254ead190f045c460564
9 (67ms)
module not found: org.scala-lang#scala-reflect;2.10.5
==== local: tried
C:\Users\ak\.ivy2\local\org.scala-lang\scala-reflect\2.10.5\ivys\ivy.xml
-- artifact org.scala-lang#scala-reflect;2.10.5!scala-reflect.jar:
C:\Users\ak\.ivy2\local\org.scala-lang\scala-reflect\2.10.5\jars\scala-reflect.jar
==== my-ivy-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/ivy-releases/org.scala-lang/scala-reflect/2.10.5/ivys/ivy.xml
==== my-maven-proxy-releases: tried
http://nexusserver:8081/nexus/content/groups/mvn-repositories/org/scala-lang/scala-reflect/2.10.5/scala-reflect-2.10.5.pom
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.scala-lang#scala-library;2.10.5: not found
:: org.scala-lang#scala-compiler;2.10.5: not found
:: org.scala-lang#scala-reflect;2.10.5: not found
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.scala-lang#scala-library;2.10.5: not found
unresolved dependency: org.scala-lang#scala-compiler;2.10.5: not found
unresolved dependency: org.scala-lang#scala-reflect;2.10.5: not found
Error during sbt execution: Error retrieving required libraries
(see C:\Users\ak\.sbt\boot\update.log for complete log)
Error: Could not retrieve sbt 0.13.9
It turned out to be an ordering issue with our Nexus proxy repositories. oss.sonatype.org maven repo was causing an issue when it was placed ahead of the Maven Central repo. Removing oss.sonatype.org maven repository solved the problem.
Related
I am trying to import sbt and other dependencies in my IntelliJ and it fails with the below error.
I have tried the solutions given at unresolved dependencies - Error while importing SBT project
but it does not work.
Below is the log of error:
Error while importing sbt project:
Java version: 1.7
VM ware : Latest Edition Licensed
Getting org.scala-sbt sbt 1.2.1 (this may take some time)...
unresolved dependency: org.scala-sbt#sbt;1.2.1: not found
(see /home/cloudera/.sbt/boot/update.log for complete log)
Error: Could not retrieve sbt 1.2.1
:: problems summary ::
:::: WARNINGS
module not found: org.scala-sbt#sbt;1.2.1
==== local: tried
/home/cloudera/.ivy2/local/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
-- artifact org.scala-sbt#sbt;1.2.1!sbt.jar:
/home/cloudera/.ivy2/local/org.scala-sbt/sbt/1.2.1/jars/sbt.jar
==== local-preloaded-ivy: tried
file:////home/cloudera/.sbt/preloaded/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
==== local-preloaded: tried
file:////home/cloudera/.sbt/preloaded/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
-- artifact org.scala-sbt#sbt;1.2.1!sbt.jar:
file:////home/cloudera/.sbt/preloaded/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
-- artifact org.scala-sbt#sbt;1.2.1!sbt.jar:
https://repo1.maven.org/maven2/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
==== sbt-maven-releases: tried
https://repo.scala-sbt.org/scalasbt/maven-releases/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
-- artifact org.scala-sbt#sbt;1.2.1!sbt.jar:
https://repo.scala-sbt.org/scalasbt/maven-releases/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
==== sbt-maven-snapshots: tried
https://repo.scala-sbt.org/scalasbt/maven-snapshots/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
-- artifact org.scala-sbt#sbt;1.2.1!sbt.jar:
https://repo.scala-sbt.org/scalasbt/maven-snapshots/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.scala-sbt#sbt;1.2.1: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
Server access Error: Received fatal alert: protocol_version url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
Server access Error: Received fatal alert: protocol_version url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/maven-releases/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/maven-releases/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/maven-snapshots/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.pom
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/maven-snapshots/org/scala-sbt/sbt/1.2.1/sbt-1.2.1.jar
Server access Error: Connection reset url=https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.scala-sbt/sbt/1.2.1/ivys/ivy.xml
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
Error during sbt execution: Error retrieving required libraries
This is a common issue with cloudera VM ware. The jdk version is 1.7 and scala 2.12 needs jdk version 1.8.
Download latest jdk and extract it on desktop. And when you open a new project for scala make sure your jdk is pointed to the latest one you downloaded.( by default it will use the jdk 1.7 which comes packged with cloudera VM ware.
Hopefully this helps.
I am usig Intellij IDEA 2017.1.5 with Scala plugin installed. I created my first Scala project with SBT. I get following error while importing SBT project:
:: problems summary :: :::: WARNINGS problem while downloading module
descriptor:
https://repo1.maven.org/maven2/org/scala-sbt/ivy/ivy/2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4/ivy-2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4.pom:
Read timed out (19336ms)
module not found:
org.scala-sbt.ivy#ivy;2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4
==== local: tried
C:\Users\Kacper\.ivy2\local\org.scala-sbt.ivy\ivy\2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4\ivys\ivy.xml
-- artifact org.scala-sbt.ivy#ivy;2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4!ivy.jar:
C:\Users\Kacper\.ivy2\local\org.scala-sbt.ivy\ivy\2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4\jars\ivy.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/scala-sbt/ivy/ivy/2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4/ivy-2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4.pom
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt.ivy/ivy/2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.scala-sbt.ivy/ivy/2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4/ivys/ivy.xml
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
::
org.scala-sbt.ivy#ivy;2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4:
not found
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS unresolved
dependency:
org.scala-sbt.ivy#ivy;2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4:
not found Error during sbt execution: Error retrieving required
libraries (see C:\Users\Kacper\.sbt\boot\update.log for complete log)
Error: Could not retrieve sbt 0.13.14 Java HotSpot(TM) 64-Bit Server
VM warning: ignoring option MaxPermSize=384M; support was removed in
8.0
I get the same error while getting sbt 0.13.15 and 0.13.14.
I got the following error when run sbt.
PS H:\> sbt
Getting org.fusesource.jansi jansi 1.11 (this may take some time)...
:: problems summary ::
:::: WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
==== local: tried
C:\Users\user1\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
C:\Users\user1\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar
==== local-preloaded-ivy: tried
file:/C:/Users/user1/.sbt/preloaded/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
==== local-preloaded: tried
file:/C:/Users/user1/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
file:/C:/Users/user1/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
Server access Error: Connection reset url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Server access Error: Connection reset url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Server access Error: Connection reset url=https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
Server access Error: Connection reset url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.fusesource.jansi#jansi;1.11: not found
Error during sbt execution: Error retrieving required libraries
(see C:\Users\user1\.sbt\boot\update.log for complete log)
Error: Could not retrieve jansi 1.11
However, I can get the file using wget?
PS H:\> wget https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
StatusCode : 200
StatusDescription : OK
Content : <?xml version="1.0" encoding="UTF-8"?>
<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 h...
......
Update:
The following error message is from update.log.
ERROR: Server access Error: Connection reset
url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Maven Central: resource not reachable for
org/fusesource/jansi#jansi;1.11:
res=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
trying
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
ERROR: Server access Error: Connection reset
url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Maven Central: resource not reachable for
org/fusesource/jansi#jansi;1.11:
res=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Maven Central: no ivy file nor artifact found for
org.fusesource.jansi#jansi;1.11 typesafe-ivy-releases: no namespace
defined: using system no ivy file in cache for
org.fusesource.jansi#jansi;1.11: tried
C:\Users\user1.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml
trying
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
ERROR: Server access Error: Connection reset
url=https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
typesafe-ivy-releases: resource not reachable for
org.fusesource.jansi#jansi;1.11:
res=https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
typesafe-ivy-releases: no ivy file found for
org.fusesource.jansi#jansi;1.11 sbt-ivy-snapshots: no namespace
defined: using system no ivy file in cache for
org.fusesource.jansi#jansi;1.11: tried
C:\Users\user1.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml
trying
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
ERROR: Server access Error: Connection reset
url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
sbt-ivy-snapshots: resource not reachable for
org.fusesource.jansi#jansi;1.11:
res=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
sbt-ivy-snapshots: no ivy file found for
org.fusesource.jansi#jansi;1.11
looks like this is not a Powershell issue at all, regardless if you're receiving the error when using Powershell. Per the top of the error, looks like you're missing dependencies:
module not found: org.fusesource.jansi#jansi;1.11
the fact that wget works but sbt doesn't is because they are entirely different applications / exe's; wget is an alias for the Powershell cmdlet Invoke-WebRequest (run Get-Command wget to see this for yourself), while sbt is it's own application that I've honestly never heard or personally.
I found the issue - need to set proxy settings for https too.
This process used to work fine in 0.11.2 but the recent change w.r.t to sbt group ID changed to org.scala-sbt (from org.scala-tools.sbt) seems to have broken a dependency.
I've got a 10.04 LTS machine to which I added the Typesafe deb repository using the deb package file, described in: https://github.com/harrah/xsbt/wiki/Getting-Started-Setup.
When I try to install from the repo I get:
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] module not found: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3
[warn] ==== typesafe-ivy-releases: tried
[warn] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/scripted-plugin_2.9.1/0.11.3/ivys/ivy.xml
[warn] ==== local: tried
[warn] /home/jasonmaclulich/.ivy2/local/org.scala-tools.sbt/scripted-plugin_2.9.1/0.11.3/ivys/ivy.xml
[warn] ==== Typesafe Repo: tried
[warn] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/scripted- plugin_2.9.1/0.11.3/ivys/ivy.xml
[warn] ==== public: tried
[warn] http://repo1.maven.org/maven2/org/scala-tools/sbt/scripted-plugin_2.9.1/0.11.3/scripted-plugin_2.9.1-0.11.3.pom
How do I instruct sbt to look for scripted-plugin at the right group id?
I also tried a manual install with this launcher (following the UNIX install instructions):
//typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.11.3-2/sbt-launch.jar
And I still get the following unresolved dependency:
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.scala-tools.sbt#scripted-plugin_2.9.1;0.11.3: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
Thoughts?
Thanks, Jason.
I thought I'd update this with how I got around it, if I explicitly set the version of sbt to 0.11.2 in my project/build.properties file, i.e., sbt.version=0.11.2.
Detected sbt version 0.11.2
Cannot find sbt launcher 0.11.2
Please download:
From http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.2/sbt-launch.jar
To /home/<username>/.sbt/.lib/0.11.2/sbt-launch.jar
I then installed the required files and I was able to continue compiling like I was used to.
While it isn't a direct solution it does let me continue with work.
I've installed latest SBT on Ubuntu successfully, but indirectly, by installing Typesafe Stack.
By now, sbt-0.11.3-build-0100 is available (http://apt.typesafe.com/pool/pool/main/s/sbt/), so you should be able to simply upgrade to solve your problem. If that doesn't work or if you're curious about the original problem, here's my diagnosis.
As you tried to do, you do need to use a new launcher for SBT 0.11.3 to use the new group ID, org.scala-sbt. Your second error message still shows a failure which refers to org.scala-tools.sbt - that's bad, and suggests you're in fact still using the old launcher.
Could you make sure that when you're launching sbt, you're launching the script you created and not the one from the Debian package? Please try using the full path for launching sbt, for instance ~/bin/sbt.
If that helps, you should fix the PATH so that ~/bin (or wherever you installed your script) comes before the directory where the system SBT is installed, which (I would say, but it's a matter of opinion) is generally useful.
I'm trying to use this fake http server project in a sbt 0.11.0 based project. Unfortunately one of it's dependencies is giving the following error:
[error] public: bad organisation found in http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom: expected='org.apache.commons' found='commons-io'
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.apache.commons#commons-io;1.3.2: java.text.ParseException: inconsistent module descriptor file found in 'http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom': bad organisation: expected='org.apache.commons' found='commons-io';
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[error] {file:/home/project_location/}default-db401d/*:update: sbt.ResolveException: unresolved dependency: org.apache.commons#commons-io;1.3.2: java.text.ParseException: inconsistent module descriptor file found in 'http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom': bad organisation: expected='org.apache.commons' found='commons-io';
From what I can tell this can be worked around by asking that ivy not check the consistency of the pom files (Maven has this setting off by default). I can't work out how to turn this off in sbt though. I tried
ivyValidate := false
but this has no effect.
Am I on the right track with this setting and is it possible to turn this setting off?
You could try to exclude this dependency and include it manually :
"se.dannej" % "fakehttpserver" % "0.1.0" exclude("org.apache.commons", "commons-io")
"commons-io" % "commons-io" % "another version"
or even download the commons-io jar and push it in your lib directory.