These bindings add to jclouds maintenance and make evolving core APIs
harder. Further they really belong outside of the jclouds repository.
I would like to remove these in 2.1.0
+1 to remove. It should be easy enough to keep them in a separate
repository dependent on jclouds, if desired. Is
Does anyone use the jclouds Clojure bindings? I raised this question
three years ago and despite some offers to help these bindings have seen
little activity:
https://lists.apache.org/thread.html/ff486477fa5af2ef944845d6b998d12b39e144e7353ba7cca532@1392843883@%3Cuser.jclouds.apache.org%3E
With my limited knowledge of Clojure, but mi willing to learn, I will make
my best to put the Chef bindings up to date, and hopefully I will then be
in a better place to give a hand in the compute bindings too.
El 30/05/2014 22:24, Everett Toews everett.to...@rackspace.com escribió:
On May 27,
On May 27, 2014, at 1:57 PM, Andrew Gaul g...@apache.org wrote:
Repeating my request for a Clojure maintainer. In addition to making
evolving the APIs more difficult, jclouds has a 3 year stale dependency
on Clojure, 1.3 vs. 1.6. I will ask the development team to drop
support unless
On Wed, Feb 19, 2014 at 01:04:43PM -0800, Andrew Gaul wrote:
Does anyone use the jclouds Clojure bindings, specifically
blobstore2.clj? These have not seen many changes over the years and
have made it harder to evolve the underlying Java jclouds APIs, e.g.,
Does anyone use the jclouds Clojure bindings, specifically
blobstore2.clj? These have not seen many changes over the years and
have made it harder to evolve the underlying Java jclouds APIs, e.g.,
https://github.com/jclouds/jclouds/pull/44 . Can someone volunteer to
maintain these?
--
Andrew
