I had similar experiences and i could work around by using activator instead of sbt.
However adding the line as suggested should be wiser than enforcing everyone to use activator. Jong Wook > On May 3, 2016, at 11:47 AM, DO YUNG YOON <[email protected]> wrote: > > Welcome to S2Graph~! > > Seems like cause and fix is obvious as you suggested. > Can you please create jira issue and it would be great if you can > contribute. > Even though fix seems trivial, If you are interested I want to ask you to > participate in our community. > If you want to contribute then I think you should submit icla( > https://www.apache.org/licenses/icla.txt) to ASF. > > > > On Thu, Apr 28, 2016 at 11:27 AM Injun Song <[email protected]> wrote: > >> I had a problem when I built the project using sbt 0.13.11 in mac osx. >> I think that lack of resolvers in plugin settings causes build failure. >> >> If you have no corresponding jars in $HOME/.ivy2/cache, sbt will says like: >> >> sbt.ResolveException: unresolved dependency: >> com.typesafe#jse_2.10;1.0.0: not found >> unresolved dependency: com.typesafe#npm_2.10;1.0.0: not found >> unresolved dependency: com.typesafe#webdriver_2.10;1.0.0: not found >> >> >> This problem will be fixed easily by adding this line into >> project/plugins.sbt: >> >> resolvers += Resolver.typesafeRepo("releases") >> >> >> Best, >> Injun Song >>
