Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please use released versions of the Riak client #2

Closed
michaelklishin opened this issue Dec 22, 2011 · 7 comments
Closed

Please use released versions of the Riak client #2

michaelklishin opened this issue Dec 22, 2011 · 7 comments

Comments

@michaelklishin
Copy link
Contributor

Please use released versions of the Riak client: 1.0.3-SNAPSHOT is not available from Maven Central or Sonatype. Not only it makes it impossible for people outside of Basho try Sumo out, it also has one more side effect: lein deps does not exit properly when it fails to find dependencies and it stalls travis-ci.org workers.

@russelldb
Copy link
Collaborator

How about if I start publishing weekly (daily??) Snapshots to sonatype? Would that work?

@michaelklishin
Copy link
Contributor Author

Weekly won't work for sumo's CI on travis-ci.org (that can be disabled for now, probably). I don't know why Sumo uses 1.0.3-SNAPSHOT and not 1.0.2 but if it has to, then please make sure said artifact is available from widely used Maven repos.

@reiddraper
Copy link
Owner

@michaelklishin I think you're right that we need to solve this. The original problem is that the released Riak Java client (1.0.2) requires Jackson 1.7.5 and Cheshire 2.0.4 requires Jackson 1.9.2. If there's another way around this, I'd much prefer it.

@michaelklishin
Copy link
Contributor Author

Would it be possible to do one release of com.basho.riak:riak-client:jar:1.0.3-SNAPSHOT today? This will both let people check Sumo out and make CI useable.

@russelldb
Copy link
Collaborator

I just published the 1.0.3-snapshot to sonatype, going to work on having our buildbot push each successful build to sonatype snapshot.

@reiddraper
Copy link
Owner

Thanks @russelldb, and sorry @michaelklishin for the trouble with usability/Travis.

@michaelklishin
Copy link
Contributor Author

With 017bb0c this issue is now resolved. Thank you everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants