On 24/08/22 15:58, Misagh Moayyed wrote:
In general, I am in favor of this approach, but just to be on the safe
side, would it make sense to deprecate the feature first? Just in case
someone out there is using it, or would keeping the code around cause
complications and maintenance issues?
Good point.
I think, however, that since we'd be doing that in a major release (e.g. 3.0)
it could be enough to add a specific section in the release notes so that in
case anyone exists that is running Syncope 2.1.x with Camel Provisioning
Manager, they are made aware that this will need to be replaced, in case of
upgrade to 3.0.0.
There are quite some breaking changes in such upgrade, the Camel Provisioning
Manager would be just one more.
Regards.
On Wed, Aug 24, 2022 at 4:16 AM Francesco Chicchiriccò
<ilgro...@apache.org> wrote:
Hi all,
working for SYNCOPE-1692, which involves some changes in the provisioning
process, I've realized that the Camel Provisioning Manager extension [1], while
featuring some very smart code has probably never been used in any production
deployment, at least none that I am aware of.
Over time, the cost of managing such (possibly unused) extension has become
quite relevant, hence I am proposing to remove it from the master branch, so
that next 3.0.0 release will not contain it anymore.
Thoughts?
Regards.
[1] https://github.com/apache/syncope/tree/master/ext/camel
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
