I think we have a consensus for alternative 1. So I will close the issue and will not apply my last patch.
Christian On 15.01.2013 15:58, Christian Schneider wrote: > So I see two alternatives: > > 1. Keep persistence inside core but try to keep it as a separate > architectural layer. This would mean to avoid cycles between persistence > and the rest of core "by hand". > 2. Only move the persistence classes to the persistence module but not > the tests. I created a patch for this in the issue above. > > > > So what do you guys think about this? > > Christian > >
