commons
commons copied to clipboard
com.twitter.common.zookeeper:server-set references non-existant com.twitter.common:service-thrift:jar:0.2.21
Hi,
I have the following in my POM:
<dependency>
<groupId>com.twitter.common.zookeeper</groupId>
<artifactId>client</artifactId>
<version>0.0.8</version>
</dependency>
<dependency>
<groupId>com.twitter.common.zookeeper</groupId>
<artifactId>server-set</artifactId>
<version>1.0.110</version>
</dependency>
Which results in:
[ERROR] Failed to execute goal on project boxever-dropwizard-extras-load-balancer: Could not resolve dependencies for project com.boxever:boxever-dropwizard-extras-load-balancer:jar:0.7.1.62-SNAPSHOT: Failure to find com.twitter.common:service-thrift:jar:0.2.21 in http://maven.twttr.com/ was cached in the local repository, resolution will not be reattempted until the update interval of twitter-twttr has elapsed or updates are forced -> [Help 1]
and indeed there is no such version at http://maven.twttr.com/com/twitter/common/service-thrift/
My guess is that the server-set pom is out of date. #346 may be related.
ping @stuhood. Did we publish again recently but miss service-thrift again?
I also notice that the version of libthrift that service-thrift pulls in is quite old, and clashes with Netflix astyanax's use of thrift.
Looks like this is still an issue, the service-thrift
version referenced in https://maven.twttr.com/com/twitter/common/zookeeper/server-set/1.0.110/server-set-1.0.110.pom (published 12 Jun 2015) appears to be 0.2.22 (which doesn't exist afaict). It appears manually specifying a recent version of service-thrift
works, e.g.:
dependencies {
compile 'com.twitter.common:service-thrift:1.0.54'
compile 'com.twitter.common.zookeeper:server-set:1.0.110'
// ...
}
@stuhood is there someone appropriate maybe on CSL you could assign this to inside Twitter's walls that has the ability to sync this stuff up?.