Future of querydsl

[Balázs Zsoldos]

Hi,

I think querydsl was one of the best things that could happen to Java. The project has a perfectly designed API that allows the programmer to solve nearly every use-case (at least querydsl-sql, which I use everywhere).

I remember that the project had the best support at the community level. However, something has been changed in the last 1-2 years. I must say, I am a bit afraid that one of the best projects will be lost in the dark and other, much worse solutions will replace it.

What happened? What can we expect? How can we help?

Does the project have financial issues? I am not rich, but I can offer a bit of money (like 10$) each month from my pocket money for a year. If enough other programmers can offer the same amount, it might be enough to make the project survive for a year that is enough time to find a more permanent solution.

Maybe the project should be separated to querydsl-jpa, querydsl-sql, ... and have separate releases. As I said, I am only interested in querydsl-sql, and I feel that regular bugfix releases could be achieved much easier if the different parts would not be handled together.

Also, if you used a service like CodeMill I would offer some money for the PRs I sent as not having a new version blocks the releases of my own libraries.

Kind regards,

Balazs

[Filipe Sousa]

👏

[Ruben Dijkstra]

For me personally, it's the lack of time.

Currently in uni, and want to graduate this (calendar) year.

I really don't know if CodeMill would be a good fit, but I haven't used it. Would it be to create incentive? Or how would you see that working?

The current release plan is in my opinion fine, just the time issue is hard to solve in my current state.

I really am itching to get back into my hobby, I've started on so many branches that I had ideas for.

So I won't let Querydsl die, but I'm just in a really rough time currently.

Br,

Ruben

[Balázs Zsoldos]

Codemill was just an example after a very quick search on Google. Maybe a popular service is bountysource is a better choice. There are several alternatives.

These are only ideas, I have sadly no experience with these services. I hope you will find a way to put more energy into the Querydsl project (so it is not a hobby project) and still be able to buy the bread for the family.

[Krzysztof Dębski]

Hi,

Some ideas:

1. Focus only on the most significant issues right now. In my opinion, Hibernate 5.2 and 5.3 incompatibility is a showstopper because it prevents from using Spring 5 and Spring Boot 2.

2. Allow some other developers to accept pull requests and make releases.

3. Donate this project to Apache Foundation

Regards,

Krzysztof

[Andy Goossens]

On Thursday, 6 September 2018 18:54:07 UTC+2, Krzysztof Dębski wrote:

Some ideas:

1. Focus only on the most significant issues right now. In my opinion, Hibernate 5.2 and 5.3 incompatibility is a showstopper because it prevents from using Spring 5 and Spring Boot 2.

2. Allow some other developers to accept pull requests and make releases.

3. Donate this project to Apache Foundation

I agree with what Krzysztof said. Except I see no point in donating this (dormant) project to Apache Foundation, at least not at the moment. It would require doing more work, more than what can be handled.

Expanding Krzysztof's list a bit:

4. Someone forks QueryDSL, releases it under another name and let it gain enough traction. Not an easy feat.

[Ruben Dijkstra]

Just want to chime in that as soon as I get more time on my hands I can dedicate more time again to my hobby.

[fasfsfgs]

Hi guys!

First of all, I understand completely this being a hobby project and not nearly as important as other things in life.

I'm now stuck at this point and I'm wondering what choices did you guys make after this.

I have to go to spring boot 2 and hibernate 5.2+ and I really didn't want to go without querydsl.

But since it's not possible now, did you guys choose another project? Stayed with hibernate 5.1? Fixed the issues on your own account? What did you all do?

Thank you all for the help.

--
You received this message because you are subscribed to the Google Groups "Querydsl" group.
To unsubscribe from this group and stop receiving emails from it, send an email to querydsl+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Krzysztof Dębski]

Hi,

I am using a custom version of Querydsl 4.2.1 with Hibernate 5.3.6 and Spring 5.1.

Do not try to use it with Hibernate 5.2. There are too many incompatible changes between 5.1 and 5.2. Most of them were reverted in 5.3.

I used maven-shade-plugin to create my versions of querydsl-core and querydsl-jpa.

I applied two patches:

1. https://github.com/querydsl/querydsl/pull/2354 (With an additional fix to SerializerBase.java line 101 - I added a comment to the pull request)

2. com.querydsl.jpa.HibernateHandler - currently it supports HibernateQuery interface only. I had to add analogous support of org.hibernate.query.internal.QueryImpl and org.hibernate.query.internal.NativeQueryImpl because these two classes do not implement HibernateQuery. In methods "addEntity" and "addScalar" I had to add support of org.hibernate.query.internal.NativeQueryImpl only. In methods "iterate" and "transform" I added support of both query types.

For example, I had to add the following to addEntity method:

} else if (query instanceof org.hibernate.query.internal.NativeQueryImpl) {
    ((org.hibernate.query.internal.NativeQueryImpl) query).addEntity(alias, type);
}

With these two fixes, everything works fine.

Regards,

Krzysztof

W dniu środa, 26 grudnia 2018 19:15:43 UTC+1 użytkownik fasfsfgs napisał:

Hi guys!

First of all, I understand completely this being a hobby project and not nearly as important as other things in life.

I'm now stuck at this point and I'm wondering what choices did you guys make after this.

I have to go to spring boot 2 and hibernate 5.2+ and I really didn't want to go without querydsl.

But since it's not possible now, did you guys choose another project? Stayed with hibernate 5.1? Fixed the issues on your own account? What did you all do?

Thank you all for the help.