opencirclesolutions / dynamo

Dynamo - Web Application Accelerator Framework
Apache License 2.0
10 stars 8 forks source link

Future of QueryDSL #269

Open tommy-ocs opened 1 week ago

tommy-ocs commented 1 week ago

Dynamo Framework makes use of QueryDSL. The project seems quite inactive/dead. We should investigate/analsye the future of the dependency on QueryDSL.

There is an active fork: https://github.com/OpenFeign/querydsl

Another option is to move away from QueryDS and embrace Spring Data, or another technology.

pdeenen commented 7 hours ago

I prefer to keep using QueryDSL due to the fluent API provided that we use to generated queries on runtime with Dynamo. So we could investigate the option to switch to the openfeign fork.

Met vriendelijke groet - Best regards, [signature_1792251818]http://www.opencirclesolutions.nl/ Patrick Deenen | R&D Director tel +31 (0)6 55 86 73 21 | @.**@.> Daalakkersweg 16-06 | 5641 JA Eindhoven | The Netherlands tel +31 (0)40 304 13 30 | www.opencirclesolutions.nlhttp://www.opencirclesolutions.nl [Facebook]https://www.facebook.com/opencirclesolutions.nl [LinkedIn] https://www.linkedin.com/company/open-circle-solutions-b-v- [LinkedIn] https://twitter.com/OpenCircleSolut

From: Tommy Menheere @.> Date: Monday, 23 September 2024 at 14:03 To: opencirclesolutions/dynamo @.> Cc: Subscribed @.***> Subject: [opencirclesolutions/dynamo] Future of QueryDSL (Issue #269)

Dynamo Framework makes use of QueryDSL. The project seems quite inactive/dead. We should investigate/analsye the future of the dependency on QueryDSL.

There is an active fork: https://github.com/OpenFeign/querydsl

Another option is to move away from QueryDS and embrace Spring Data, or another technology.

— Reply to this email directly, view it on GitHubhttps://github.com/opencirclesolutions/dynamo/issues/269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABAOKNKG3BA6R6ESOUCJ7JDZX77QPAVCNFSM6AAAAABOV5KINGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DENBSGQ3DGMI. You are receiving this because you are subscribed to this thread.Message ID: @.***>