Hi, I merged my suggestion for 'refactoring project structure' and 'refactoring folder structure' into an issue, see "https://issues.apache.org/jira/browse/OLINGO-23";.
I take Stephan's "+1" and wait for more opinions or better solutions ;o) Kind regards, Michael On 23.09.13 16:05, "Klevenz, Stephan" <[email protected]> wrote: >+1 for refactoring the folder structure > > > >On 23.09.13 15:45, "Bolz, Michael" <[email protected]> wrote: > >>Hi, >> >>For improving our current documentation/tutorials I want to create a new >>sub-folder named 'odata-sample' were I then put the sample project for >>the tutorial. >>This sample will be de-coupled from the odata library pom so that it is >>not handled as a maven sub module. >> >>Currently I have done this in a separate branch (named: "samples") so >>that everybody can check it out and we can discuss if this is the way to >>go. >>This suggestion is also based on my recommendation of a changed project >>structure (see below attached part of my mail from 11/09). >> >>What do you think about it? Any better solutions? >> >>Kind regards, >>Michael >> >>Folder structure: >>/ >>-> odata2-processor-jpa >> --> processor-api >> --> processor-core >>-> odata2-lib >> --> odata2-api >> --> odata2-core >> --> odata2-testutil >> --> odata2-fit >> --> odata2-ref >> --> odata2-ref.web >>-> odata2-sample [NEW] >> --> odata2-cars-service [NEW] >> --> odata2-cars-web [NEW] >
