Querydsl: Is querydsl dead?

[reegnz]

Hi,

I cannot fail to notice that the project has 249 outstanding issues, 32 PR-s, no merges since february, etc.
Is the project dead?

I think there are more than a few people willing to help resolve issues, but at this pace of merging it hardly motivates people to use querydsl at all.

Not sure how other people do this, but for me if a project has outstanding issues but no commits since months, that's a red flag, and I won't be using that tool.

Please either resolve the issues without fixes, or onboard someone to help out.

Keeping the project in this seemingly dead state won't help and it would be a shame if people don't use this awesome tool just because it looks like it's abandoned.

Thanks,
A concerned user of querydsl

[Shredder121]

I've been trying to get a hold of the members, don't worry it's not abandoned.
As of this writing the person who has a release profile set up is Timo, and I've not tried setting mine up yet because of warnings when I package for release.
Also, this was already asked in the Google group.

[wenerme]

Is it really not abandoned? 294 issues, 40 pr now, no more update since feb 21, what happened ?

[Shredder121]

It's not abandoned, I'm still working on it, but I have no way of releasing com.mysema artifacts just because they are com.mysema artifacts.
Me explaining this again and again becomes tiring.
At least thanks for your concern.
I'll pick stuff back up after the holidays.

[reegnz]

If it's just not being able to release, why not still merge PR-s, and eventually release when you guys sort it out?

[natros]

It seems that @timowest does not care about this project anymore. We can't wait forever. Can't we replace mysema or rename it? Fork the project?

[ChristianCiach]

I was just about to introduce QueryDSL to our enterprise product, but I agree, this project seems to be abandoned. The last release was 30.6.2016. A real bummer, but I can't use libraries that are dead on arrival.

[Shredder121]

I quite literally just asked Timo to release soon (he can still do releases, I asked him to release this weekend or whenever he can).
We do have some changes we can release.
Now, I don't feel like locking threads or topics over the hiatus, it happened, no denying that, but it's getting rather old.
Anyway, thanks for sticking with us! We'll get a release out again soon.

[ChristianCiach]

Thanks for your quick reply!

But to be honest, I find it kinda worrying that the rise and fall of the project (and its releases) depends on a single person, who (to the best of my knowledge) didn't state anything himself about the long downtime of the project. I think it is important to lessen the dependence on a single person to ensure the continuation of QueryDSL even if one or more persons drop out for any reason.

[Shredder121]

But to be honest, I find it kinda worrying that the rise and fall of the project (and its releases) depends on a single person
I think it is important to lessen the dependence on a single person to ensure the continuation of QueryDSL

I agree, currently also looking into automating things, so not everything hinges on one person. Or requiring a specific person for that matter.

[martinsefcik]

@Shredder121 @timowest
One year with no commit to repository, more then 400 open issues and 49 open merge requests. So I would like to ask the same question again: Is querydsl dead?

[tpischke-bedag]

No activity in a year. This is making us very nervous, to the point that our company is starting to look into alternatives to QueryDSL. I hope to see a clear commitment or some renewed activity very soon.

[jherkel]

I don't understand that someone from owners cannot make a statement about future of querydsl. For example, project is dead try to fork it or try to find some alternatives.

[Shredder121]

No activity in a year. This is making us very nervous, to the point that our company is starting to look into alternatives to QueryDSL. I hope to see a clear commitment or some renewed activity very soon.

I only have a few days per month time, and actually only to check emails. I'm still currently in the middle of university, which is already delayed quite a bit.
When I get that finished I can dedicate time again to hobbies, I still love Querydsl, there just isn't enough time in my schedule to make things work at the moment.

[jherkel]

Thanks for sharing some information about status of project but could you be more specific? I really understand that you don't have time now but how long will it take? If there will be another year without any real activity I'm afraid that it will mean more or less death of querydsl. I understand that it is your spare time activity but if you don't have time couldn't it be a way that someone from community will have access to github and he/they could review pull request and prepare release from time to time? It will be sad if truly awesome project like querydsl would end because of your lack of time...

[pslootweg]

The situation was about the same a year ago: https://groups.google.com/forum/#!topic/querydsl/-1bEVeE2kiU

I gather others have offered to get involved (even some large players) and would have thought that would be a great way to allow this to stay alive.

[vnobo]

so?

[limkinZero]

So it's dead

[pslootweg]

Look folks, the repo owner hasn't contributed in 2 years!
Of the 3 developers, only @Shredder121 seems to take any notice of its existence - the other two not at all.

Time to look at https://www.jooq.org/ or fork queryDsl and maintain your own version.

[natros]

+1 fork

[robertandrewbain]

I agree it should be forked.

[thackel]

jOOQ is not a replacement for Querydsl. Its only for pure SQL and has a restrictive license for Enterprise Databases.
Querydsl can be used with any Database which is supported and the most important, it can be used with JPA.

But i agree with the others that forking seems to be the only solution to keep this important masterpiece up to date.

[gardengeek99]

+1 Fork

[pslootweg]

jOOQ is not a replacement for Querydsl. ...

When I evaluated both side-by-side (and it was a while ago...) there was not a lot between them.
Most important - it has moved on!

But i agree with the others that forking seems to be the only solution...

I agree, but - that will most likely end up with as many divergent implementations as there are forks.

[limkinZero]

We need fork and promote the "new" framework. The probrem is the domain of web hosting. We should keep doc, ... In AWE framework, we use queryDsl for all data engine.

[pslootweg]

Maybe persuade @timowest to hand it over to someone?

[jalati-paychex]

Maybe persuade @timowest to hand it over to someone?

I agree, perhaps transition is more appropriate than complete fork.

[vnobo]

Maybe persuade @timowest to hand it over to someone?

How to do?

[Maia-Everett]

How to do?

Send him an email, maybe? There is one in his profile.

[hadri3n]

Hi,
I am a nobody, have no credits, (open-source-wise) nothing to show for, but I used and still use Querydsl on at least 3 of my active projects.

I don't think we should look the other way and try to look for alternatives immediately.
I believe this is a great lib and I am pretty sure a substantial amount of projects rely on it.

I as well don't think one man (@Shredder121) can provide alone the necessary time to address issues, and maintain the code base.

I do think that precisely because a lot of projects rely on it, a lot of people should have an interest in investing a bit of time (should it be a few hours) looking into issues (at least the one they face) and offering if not solutions, conclusions from their investigations.
Because the time they invest in fixing the lib is time they will not have to invest in learning another one and refactoring their project(s).

I am more than willing to allocate time to help in any way I can.
I have no way to contact you directly @Shredder121, but if you are still up for it, we could get in touch...

Long live Querydsl ? :-)

[cdalexndr]

I have started to slowly migrate from QueryDSL to JOOQ. You need additional helper methods to query JPA using entityManager, but it is doable. Plus it supports additional features like create temporary table that I needed in my project. Also I'm using open source Postgres DB, so free license JOOQ.

The problem with QueryDSL is that it's stuck with hibernate 5.1.x and spring 4.x old versions.
I just found a bug that is fixed in spring 5 but not in spring 4, so the old versions are becoming a real issue.

[michal-kroliczek]

OMG this looks like javascript lib. Start with doing nice job for some time, then ... then nothing. Even no replies from creators. Hate this

[vnobo]

OMG this looks like javascript lib. Start with doing nice job for some time, then ... then nothing. Even no replies from creators. Hate this

2459

[ekermawi]

its going back to life
read this
https://github.com/querydsl/querydsl/issues/2459

[InternetPseudonym]

The problem with QueryDSL is that it's stuck with hibernate 5.1.x and spring 4.x old versions.

Uhm ... QueryDSL does not care about your hibernate and/or spring versions - im using spring 5 and a pretty recent hibernate version (5.3.9) ; no problems whatsoever. I think you might want to fix your setup, obviously there are some dependency problems unrelated to QueryDSL

[cdalexndr]

@InternetPseudonym see unresolved Issue2264 related to hibernate 5.2 support.