Michael Bolz created OLINGO-23:
----------------------------------
Summary: Refactoring project (folder) structure
Key: OLINGO-23
URL: https://issues.apache.org/jira/browse/OLINGO-23
Project: Olingo
Issue Type: Task
Reporter: Michael Bolz
Before we build a initial release I suggest we clean up our root project folder
and create some sub folders.
My suggestion (from mailing list) is a separate folder for the core library,
for library extensions and for samples. Currently this results in a separation
between "odata2-lib", "odata2-processor-jpa" and "odata2-samples" as shown
below.
In addition we probably need to adjust the pom structure (as shown below).
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-samples [NEW]
--> odata2-cars-service [NEW]
--> odata2-cars-web [NEW]
According project structure:
org.apache.olingo.odata2-parent
-> org.apache.olingo.odata2-processor.jpa
--> org.apache.olingo.odata2-jpa.processor.api
--> org.apache.olingo.odata2-jpa.processor.core
-> org.apache.olingo.odata2-lib
--> org.apache.olingo.odata2-api
--> org.apache.olingo.odata2-core
--> org.apache.olingo.odata2-testutil
--> org.apache.olingo.odata2-fit
--> org.apache.olingo.odata2-ref
--> org.apache.olingo.odata2-ref.web
-> org.apache.olingo.odata2-samples
--> org.apache.olingo.odata2-tutorial [NEW]
--> org.apache.olingo.odata2-tutorial.web [NEW]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
