2.2 : code refactoring

[florent andré <fl...@4sengines.com>]

Hi all,

As I have a deep look at the Lenya code base theses days, I notice that
lenya-core-api and lenya-core-impl have plenty of code and large package
coverage (packages that are related to some others modules).

Moreover, lenya-core-api have many implementations in it and not only
interfaces.

So I decide to :
- extract all interfaces from core-api and move them to core-impl.
- and after that dispatch code into related modules
(o.a.l.cms.repository into core-impl move to core-repository for example).

This process brings me to create :

- lenya-core-cocoon : keep all related cocoon components

- lenya-core-publication : as publication is an important things in
Lenya  this have to had is proper module.

So core-api/impl have been dispatch into this mains components :
- core-publication
- core-repository
- core-workflow
- core-observation
- core-cocoon
- core-metadata

The strange things - I think - it that we don't have some "document"
component. As I see, most of the "document" implementation is done
inside the publication.

The next step - after rearrange all maven dependencies - will be to
split this main components into
- core-componentName-api
- core-componentName-impl

Where api just contain existing interfaces.
This will allow to define a stable - shareable - api, and more easily
change componentName-impl if needed.

As I also would like to change some package names, I may create some
core-componentName-deprecated, that will allow ascendant compatibility.

++



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org