Hi, yes we should move the fit module to the top level. I can do this during refactoring today.
Best Regards, Christian -----Original Message----- From: Francesco Chicchiriccò [mailto:[email protected]] Sent: Freitag, 7. März 2014 17:10 To: [email protected] Subject: Re: [DISCUSS] Where to merge modules from ODataJClient? On 07/03/2014 17:03, Klevenz, Stephan wrote: >> I'd propose for (1) a new top-level module (at the same level of >> odata4-lib) named odata4-test-service. >> WDYT? > There is already a module for this kind of purpose: > olingo-odata4-fit-incubating > > > FIT stands for full integration test and in odata2 it had following > properties: > > - test start a server (mock or reference scenario) > - test runs over http > > To have the module on top level makes sense, because it can then be used > to test extensions as well. I don't care about if we name it fit or > test. > > So, from me +1. > > But we should have one. And at the end it would be cool to have > integrated tests where the client runs against the server. Shall we move then odata4-fit from odata-lib/ to toplevel and move there the content of ODataJClient/test-service? The idea is that odata4-client-core (and also the new module for proxy) will start odata4-fit and then perform all integration tests in the Maven verify phase via the failsafe plugin. Regards. > On 07.03.14 15:54, "Francesco Chicchiriccò" <[email protected]> wrote: >> Hi, >> so far we've been merging the former 'engine' module from ODataJClient >> into odata4-client-api and odata4-client-core (there is still a lot to >> do, of course). >> >> There are, however, more modules we need to merge from ODataJClient: >> >> 1. test-service - a simple CXF-based application which acts as V3 and >> V4 service (with static back-end) for integration tests of the 'engine' >> and 'proxy' modules (Fabio is working to complete this as per OLINGO-175) >> >> 2. maven-plugin - the Maven plugin for generating POJOs to be used >> with the 'proxy' module >> >> 3. proxy - Inspired by JPA, this layer will convert any local change >> to POJOs and any local invocation of annotated interfaces' methods into >> actual calls to the Engine layer. >> >> >> While (2) and (3) will be merged later, we need to find the right place >> for (1) ASAP in order to start merging all remaining components and >> integrations tests from the 'engine' module. >> >> I'd propose for (1) a new top-level module (at the same level of >> odata4-lib) named odata4-test-service. >> WDYT? -- 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/
