Have a look at [1] and [2]. There are (potential) other sub-modules which are not considered in current project structure.
[1] https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=tree;f=ODataJ Client;h=30a990db32e4abd971b43e8bb31a0105d281cbae;hb=HEAD [2] https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=tree -- Stephan On 28.04.14 15:04, "V.A, Chandan" <[email protected]> wrote: >Hello All, >I did not get the use case. Can you please explain what is the use case >behind using maven plugin for JPA processor. > >Thanks, >Kind Regards >Chandan VA > >-----Original Message----- >From: Klevenz, Stephan [mailto:[email protected]] >Sent: Monday, April 28, 2014 6:28 PM >To: [email protected] >Subject: Re: [DISCUSS] Migrating ODataJClient's maven plugin and proxy >layer > >Good point. > >It is also an option to have such kind of extensions for the server, e.g. >JPA-processor or JDBC-processor, like we have it already for OData 2.0. > >What about to keep top level lean and introduce ext for extensions? > >/fit >/lib >/ext (for extensions) > /client-proxy > /JPA... > >Alternatively we can skip <ext> and put extensions flat on top level. > >Do you have preferences? > >-- Stephan > >On 28.04.14 09:51, "Francesco Chicchiriccò" <[email protected]> wrote: > >>Hi all, >>we have in practice finished the merge of ODataJClient's Engine layer: >>we need now to merge: >> >> 1. odatajclient-maven-plugin: the Maven plugin for generating POJOs >>against a certain OData service, to be used by the Proxy layer >> 2. the Proxy layer >> >>Which names / locations would you suggest for them? >>Regards. >> >>-- >>Francesco Chicchiriccò >> >>Tirasa - Open Source Excellence >>http://www.tirasa.net/ >> >>Involved at The Apache Software Foundation: >>member, Syncope PMC chair, Cocoon PMC, Olingo PMC >>http://people.apache.org/~ilgrosso/ >> >
