You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Klevenz, Stephan" <st...@sap.com> on 2014/02/17 10:09:42 UTC
Code arrived, next steps?
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?
Regards,
Stephan
RE: Code arrived, next steps?
Posted by "Amend, Christian" <ch...@sap.com>.
Hi,
+1 from me as well.
Best Regards,
Christian
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Dienstag, 18. Februar 2014 11:49
To: dev@olingo.incubator.apache.org
Subject: Re: Code arrived, next steps?
+1
Feature branches are really cool in git. We are doing the same for major
code changes.
Stephan
On 18.02.14 10:56, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>Hi all,
>is it fine that I try to merge
>
>ODataJClient/engine/src/main/java/com/msopentech/odatajclient/engine/metad
>ata/
>
>with
>
>odata4-lib/odata4-commons-api/src/main/java/org/apache/olingo/odata4/commo
>ns/api/edm/
>
>in a new 'odatajclient-merge' branch?
>
>In this way I should be able to periodically sync from master branch and
>eventually resolve odatajclient-merge into master, without blocking
>other people doing their actual work.
>
>Please let me know.
>Regards.
>
>On 17/02/2014 12:42, Klevenz, Stephan wrote:
>> +1
>>
>> Sounds good.
>>
>> Our effort currently goes into server side edm and uri parser. Next
>>target
>> is to get metadata and service document serialization.
>>
>> - Stephan
>>
>>
>> On 17.02.14 10:39, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>>
>>> 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/
>
Re: Code arrived, next steps?
Posted by "Klevenz, Stephan" <st...@sap.com>.
+1
Feature branches are really cool in git. We are doing the same for major
code changes.
Stephan
On 18.02.14 10:56, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>Hi all,
>is it fine that I try to merge
>
>ODataJClient/engine/src/main/java/com/msopentech/odatajclient/engine/metad
>ata/
>
>with
>
>odata4-lib/odata4-commons-api/src/main/java/org/apache/olingo/odata4/commo
>ns/api/edm/
>
>in a new 'odatajclient-merge' branch?
>
>In this way I should be able to periodically sync from master branch and
>eventually resolve odatajclient-merge into master, without blocking
>other people doing their actual work.
>
>Please let me know.
>Regards.
>
>On 17/02/2014 12:42, Klevenz, Stephan wrote:
>> +1
>>
>> Sounds good.
>>
>> Our effort currently goes into server side edm and uri parser. Next
>>target
>> is to get metadata and service document serialization.
>>
>> - Stephan
>>
>>
>> On 17.02.14 10:39, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>>
>>> 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/
>
Re: Code arrived, next steps?
Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi all,
is it fine that I try to merge
ODataJClient/engine/src/main/java/com/msopentech/odatajclient/engine/metadata/
with
odata4-lib/odata4-commons-api/src/main/java/org/apache/olingo/odata4/commons/api/edm/
in a new 'odatajclient-merge' branch?
In this way I should be able to periodically sync from master branch and
eventually resolve odatajclient-merge into master, without blocking
other people doing their actual work.
Please let me know.
Regards.
On 17/02/2014 12:42, Klevenz, Stephan wrote:
> +1
>
> Sounds good.
>
> Our effort currently goes into server side edm and uri parser. Next target
> is to get metadata and service document serialization.
>
> - Stephan
>
>
> On 17.02.14 10:39, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>
>> 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/
Re: Code arrived, next steps?
Posted by "Klevenz, Stephan" <st...@sap.com>.
+1
Sounds good.
Our effort currently goes into server side edm and uri parser. Next target
is to get metadata and service document serialization.
- Stephan
On 17.02.14 10:39, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>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/
>
Re: Code arrived, next steps?
Posted by Francesco Chicchiriccò <il...@apache.org>.
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/