featherbed
featherbed copied to clipboard
Can't import via sbt
Using the "git method" seems to fail, and featherbed is not published on maven.
In the meantime I've cloned this repo and run sbt publishLocal to get it into my local .ivy2
It'd be good to get the basic import featherbed.Client statement for featherbed into the README as well, it was a little confusing to see it fully-qualified everywhere in the docs.
What is the reason behind it not being on maven yet?
It's published to the Sonatype Snapshot repo. As per https://finagle.github.io/featherbed/doc/01-installation.html, in sbt:
resolvers += Resolver.sonatypeRepo("snapshots")
libraryDependencies ++= Seq(
"io.github.finagle" %"featherbed_2.11" %"0.2.1-SNAPSHOT"
)
Jar file can be successfully downloaded. But beside a MANIFEST there is nothing.
Archive: .ivy2/cache/io.github.finagle/featherbed_2.11/jars/featherbed_2.11-0.2.1-SNAPSHOT.jar
Length Date Time Name
--------- ---------- ----- ----
299 2016-09-02 14:43 META-INF/MANIFEST.MF
--------- -------
299 1 file
@yeyan adding featherbed as an sbt dependency causes featherbed-core to be included transitively. featherbed itself doesn't contain anything.
After changing dependency from
"io.github.finagle" %% "featherbed" %"0.2.1-SNAPSHOT" to
"io.github.finagle" %% "featherbed-core" %"0.2.1-SNAPSHOT"
Featherbed-core is successfully fetched. The documentation on in Guide is bit confusing. It should change from
resolvers += Resolver.sonatypeRepo("snapshots")
libraryDependencies ++= Seq(
"io.github.finagle" %"featherbed_2.11" %"0.2.1-SNAPSHOT"
)
to
resolvers += Resolver.sonatypeRepo("snapshots")
libraryDependencies ++= Seq(
"io.github.finagle" %% "featherbed-core" %"0.2.1-SNAPSHOT"
)
By the way sbt can not find anything like featherbed-circle. Does that lib published to repo yet?
It's circe, not circle.
It would be great if "io.github.finagle" %% "featherbed-core" %"0.2.1-SNAPSHOT" would be mentioned in the installation
This was fixed in 0.2.2 for me (see #57) and there doesn't seem to be any recent complaints regarding this issue, so I suggest it can be closed.