On 17/02/2014 10:09, Klevenz, Stephan wrote:
Eduard, et al,
Code is arrived. Big thank you for this contribution!
Now we have to think about next steps. Areas for discussion are:
* projects directory structure for client, server, commons
* Java package structure
* Maven build with one parent pom for all
* license header for all source files
Are there any comments or suggestions on this?
Hi Stephan,
here is a quick overlook of feature-oriented activities we planned
*before* knowing that code will have moved to Olingo4:
1. Implement Version abstraction layer, Metadata parser and Types -
completed
2. Implement URIBuilder and FilterBuilder, Request / Response
handling, Navigation Properties, (De)serializers: Atom and JSON
3. Implement Asynchronous management, Batch operations, Actions and
Functions enhancements
Moreover, currently I am working on V4 Atom (de)serializer , while Fabio
and Massimiliano are targeted to replace the private external V3 service
used in the it profile with a local static service (in the test-service
module); this activity has also the purpose of providing a V4 static
test service (waiting for Olingo V4 server to be complete).
Including the items you report above, I'd propose the following schedule:
a. complete Fabio's and Massimiliano's activities under ODataJClient/
(it should take a week or more to complete, there are about 400
integration tests to migrate)
b. immediately adapt license headers to ASF (I can handle this)
c. complete [1] for project directory structure (including the root
pom.xml) and package names; I'd leave the current ODataJClient/
directory out of this process
d. move stuff from ODataJClient/ to the new structure and eventually
remove ODataJClient/
e. finally complete V4 features
WDYT?
[1] https://wiki.apache.org/Olingo/Olingo%20Module%20Proposal
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PPMC
http://people.apache.org/~ilgrosso/
