Hi, >From me it is also a +1 for 1., 2., A and B.
I also think we should have fixed dependencies for the reference scenarios. They should work without having to configure much to make it easier for new developers to understand how to develop an OData service. Best Regards, Christian -----Original Message----- From: V.A, Chandan [mailto:[email protected]] Sent: Sonntag, 25. August 2013 07:19 To: [email protected] Subject: RE: distributions Hi, +1 for [1] and [2]. Can we also distribute 3. Reference scenario for OData Lib 4. Reference scenario for OData JPA Lib The reference scenario could use a specific version of dependency for example CXF, Eclipse Link 2.5.0 in case of JPA. Secondly Should we also consider separate distributions in the download page for A. JARs with no source code B. JARs + source code + java docs as one bundle In case developers don't have experience with git, then they can directly download the source code from the download page as .zip format. Thanks, Kind Regards Chandan VA -----Original Message----- From: Klevenz, Stephan [mailto:[email protected]] Sent: Friday, August 23, 2013 1:34 PM To: [email protected] Subject: distributions Hi, To get a first release we have to think about distributions which we can put onto a download page. Basically I do see this kinds of distributions: 1. OData Lib (api + core + dependencies) 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more dependencies) About the dependencies: I suggest not to bundle a specific Apache CXF version. The project uses a specific CXF version (currently 2.7.5) only for testing and the lib should work also with other versions. Potentially any JAX-RS implementation should work. WDYT? Regards, Stephan
