Hi all, I also agree to both.
> I agree with you: I don't think that the JS library might ever share > something significant with the Java artifacts, so a separate repository > (olingojs?) makes sense to me. Separate Git repository for Java and JavaScript artifacts. So both can be keeped clean with their own dependencies. > About ODataJClient, it is currently 100% compatible V3 and we have recently > started supporting the V4 spec, hence I'd say its best suiting repository is > olingo4. Great to here that the ODataJClient is going to support V4 spec. I am currently writing on an example/how to use our current Olingo/OData as a client library and by the way I realized that our library miss some API functions to really work perfect in the client case ;o) Kind regards, Michael
smime.p7s
Description: S/MIME cryptographic signature
