Thanks, by 'the merge from ODataJClient to finish', do you mean end of March? Or when everything is completed? Pls let me know when you think it is an appropriate time with least conflicts with your commits.
Thanks,-Challen -----Original Message----- From: Francesco Chicchiriccò (JIRA) [mailto:j...@apache.org] Sent: 2014年3月17日 16:39 To: dev@olingo.incubator.apache.org Subject: [jira] [Commented] (OLINGO-191) use general namespace for lastest version. [ https://issues.apache.org/jira/browse/OLINGO-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937551#comment-13937551 ] Francesco Chicchiriccò commented on OLINGO-191: ----------------------------------------------- As said previously, I don't see any advantage in this. Using at least something like as {{org.apache.olingo.client.api.edm.current}} looks a bit better. Again, I'd suggest you to wait for the merge from ODataJClient to finish before entering in such package renaming: doing so, you will help reducing the effort currently required to translate ODataJClient's code to Olingo. > use general namespace for lastest version. > ------------------------------------------ > > Key: OLINGO-191 > URL: https://issues.apache.org/jira/browse/OLINGO-191 > Project: Olingo > Issue Type: Task > Components: odata4-client > Affects Versions: V4 0.1.0 > Reporter: Challen > Fix For: V4 0.1.0 > > > open this JIRA for versioning namespaces [1]. > For example: > org.apache.olingo.odata4.client.api.edm > org.apache.olingo.odata4.client.api.edm.v3 > org.apache.olingo.odata4.client.api.edm.v4 > ==> > org.apache.olingo.client.api.edm.shared > org.apache.olingo.client.api.edm.v3 - for v3 > org.apache.olingo.client.api.edm - for v4 > [1] http://markmail.org/message/27ctcvjmujbii6po -- This message was sent by Atlassian JIRA (v6.2#6252)
