Hi Francesco, > Gesendet: Donnerstag, 11. Dezember 2014 um 13:48 Uhr > Von: "Francesco Chicchiriccò" <ilgro...@apache.org> > An: dev@syncope.apache.org > Betreff: Re: [PROPOSAL] Code re-organization for Apache Syncope 2.0
> >> I have put a proposal at [1] - as you can see it is an empty skeleton > >> with README.md on each directory explaining the purpose of the > >> related module. > >> My idea is to start this (huge) refactoring for Apache Syncope 2.0, > >> e.g. on a new branch. > >> > >> WDYT? > > > > I see it with mixed feelings... > > > > Actually the new code organization looks good, and it is a good thing > > to refactor the growing codebase for > > better maintainability and extendability. > > > > On the other hand, I'd expect considerable upgrade effort/risk for > > projects (like ours) based on the current archetype and including > > custom modifications. > > Do you think one could provide an appropriate upgrade path for such > > projects? > > Hi Guido, > I was actually expecting similar concerns from your side :-) > > As you've recently seen with 1.2, we always provide an upgrade procedure > (with supporting module, if needed), and I think we should keep this way > also for 2.0. > Naturally, there are some limitations, the procedure can't be > bullet-proof for each and every scenario, but it has to be good enough > for easing the upgrade process with reasonable effort. Sounds good. I just wanted to emphasize that some attention should be paid during a possible code restructuring that migration of projects based on the current archetype is feasible. "copy any existing Java class ... and make necessary adaptations" in the upgrade guide to 1.2 sounds easier than it was ;-) Cheers, Guido
