Hi Michael On Dec 22, 2014 6:23 AM, "Bolz, Michael" <[email protected]> wrote: > > Hi all, > > during merge and integration of "OLINGO-193 - Spring Support [1]" into the main branch I though about the idea to do a clear separation between the main Olingo OData library and extensions like JPA processor, Java Annotation processor or this Spring support extension. > This could be reached with creation of a separate repository just for such extensions and that each extension is not a maven sub project (extending the Olingo pom) but extending directly the Apache parent pom. > > The positive points are: > - That the core Olingo library and all extensions will be clearly separated
Are they not separated enough today (hierarchically in the file system) ? > - It would be easier to release them distinct from the main library (and vice versa) Do we really need a separate repository to achieve this? Consequently, shouldn't you propose a repository per extension in this case? > - Integration of another new extension in future would be easier Another new repository? > > The negative points is that we need another git repository. Consequently many! > > What do you think about such an idea? This is my personal opinion, I don't believe multiple repositories makes anything easier. If someone works on an extension she will most probably want the core sources checked out as well. So what do we positively gain with multiple repositories? I'd propose to refactor current layout if we want to achieve separate life cycles of different modules if it isn't already good enough. > > Kind regards, > Michael > > [1]: https://issues.apache.org/jira/browse/OLINGO-193 -- Giacomo Pati
