FYI I went ahead and opened
https://github.com/apache/syncope/pull/371
with purpose of following up with action after discussion here.
About 2_1_X , I don't think we should change anything.
Regards.
On 25/08/22 09:24, Andrea Patricelli wrote:
Hi all,
Even if I agree with Misagh, I can
Hi all,
Even if I agree with Misagh, I can confirm that even customers that were
interested in the camel extension finally decided not to use it in favour
of extending the default one.
So agree on removing this feature on master.
Just to know, we're going to upgrade camel deps and support it on
Hi Francesco, I completely agree with you.
I do think we should keep the entire project as simple as possible.
So, removing unused and quite useless extensions could be the right approach.
Regards,
F.
On Wed, Aug 24, 2022 at 1:16 PM Francesco Chicchiriccò
wrote:
>
> Hi all,
> working for
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?
No objection from my side.
Regards
JB
On Wed, Aug 24, 2022 at 1:16 PM Francesco Chicchiriccò
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
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?
On Wed, Aug 24, 2022 at 4:16 AM Francesco
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
