[
https://issues.apache.org/jira/browse/OLINGO-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937543#comment-13937543
]
Challen commented on OLINGO-191:
--------------------------------
Hi Francesco,
The reason behind my changes is as below. Since you are writing client codes,
so hope you can help to review it.
I can image there will be problem with having version number in namespace. For
example, by some chance we may have v5, then:
org.apache.olingo.client.api.edm
org.apache.olingo.client.api.edm.v3
org.apache.olingo.client.api.edm.v4
org.apache.olingo.client.api.edm.v5
no matter there is breaking change or not, user needs to change their 'import'
everywhere:
import org.apache.olingo.odata4.client.api.edm.v4 ==> import
org.apache.olingo.odata4.client.api.edm.v5
so basically I am proposing:
org.apache.olingo.client.api.edm.shared
org.apache.olingo.client.api.edm.v3
org.apache.olingo.client.api.edm.v4
org.apache.olingo.client.api.edm --> a fixed name without version number for
latest release, while older versions have their versioned namespaces.
Do you think it make sense? (I am ok with a different but reasonable name like
org.apache.olingo.client.api.edm.current for the latest release.)
Thanks,-Challen
> 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)
