CODEWITHSUNDEEP
scalasbt
Brent Saunders
Brent Saunders

Reputation: 1

sbt unresolved library dependencies

sbt compile issues unresolved dependencies error

Research SBT configuration. I do have the correct syntax. But SBT still issues error

name := "MyProject"

version := "1.0"

scalaVersion := "2.11.12"

resolvers += 
  "Sonatype OSS Snapshots" at "https://oss.sonatype.org/content/repositories/releases"

libraryDependencies += "java.io.IOException" % "IOException" % "latest.integration"

libraryDependencies += "java.io.FileReader" % "FileReader" % "latest.integration"

libraryDependencies += "java.io.FileNotFoundExceptiom" % "FileNotFoundException" % "latest.integration"

I have a working scala program. I expect the dependencies to be included instead I receive the following Warning. What am I missing? Warning Message

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: java.io.IOException#IOException;latest.integration: not found
[warn]  :: java.io.FileReader#FileReader;latest.integration: not found
[warn]  :: java.io.FileNotFoundExceptiom#FileNotFoundException;latest.integration: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

Upvotes: 0

Views: 116

Answers (1)

pedrorijo91
pedrorijo91

Reputation: 7865

hmm, there's something weird.

Typically you declare dependencies in a form of a lib/jar that does contain a set of classes, and not the individual class itself.

In your specific case, you don't even need to add any dependency to get java.io.* classes since it belong to standard library and are included by default

Upvotes: 1

Related Questions