search

couchbaselabs / couchbase-lite-android-ektorp

Ektorp adapter for couchbase-lite-android
Apache License 2.0
3 stars 2 forks source link

Missing CBLite in maven repo #7

Open S-o-l opened 9 years ago

S-o-l commented 9 years ago

I tried to use CBLiteEktorp-1.0.0-beta2 yesterday but keep getting the following error message

Could not find com.couchbase.cblite:CBLite:1.0.0-beta2.

After looking at the CBLiteEktorp pom file in the maven repository(http://files.couchbase.com/maven2/com/couchbase/cblite/CBLiteEktorp/1.0.0-beta2/CBLiteEktorp-1.0.0-beta2.pom) I saw the following dependency: com.couchbase.cbliteCBLite1.0.0-beta2compile But there is no CBLite in http://files.couchbase.com/maven2/com/couchbase/cblite/ Maybe it was removed or something...

tleyden commented 9 years ago

It looks like this was accidentally removed during a cleanup of our maven repo.

Since we now have a native java api for accessing couchbase lite, the ektorp adapter is no longer officially supported by couchbase.

I'm hoping that members of the community that are using this module will step forward as maintainers.

RicardoBelchior commented 9 years ago

hi @tleyden

we've been using the ektorp adapter (in production) for a while now and want to update our source base. when you say, "now we have a native java api for accessing couchbase lite", what are you referring to? and in what way does it replace ektorp?

tleyden commented 9 years ago

@RicardoBelchior the native api is documented here: http://developer.couchbase.com/mobile/develop/references/couchbase-lite/couchbase-lite/index.html

nlight-jdev commented 8 years ago

@tleyden - I'm sorry but didn't understand how does the native api replace Ektorp.

Ektorp has mapping directly into java beans, while native api is more low level. Why would you use the native api? Is it related to the philosophy of nosql databases and that you're not supposed to map directly to java beans like in RDBMS?

Also, why was Ektorp deprecated?

Thanks!