Servlet 4.0/5.0

[Vitaliy L]

Hi All,

Are there plans for supporting Servlet 4.0 or 5.0 (Jetty 10.0.x or 11.0.x)? Maybe someone already reviewed what should be done to bring support?

Thanks & Regards,

Vitalii

[Matt Farmer]

No current plans at the moment. Most of us on the committer list have been busy with personal life stuff for awhile now. That said, this is probably one of those things we should look more closely at.

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/a41b0ae5-4e83-4886-b501-b349a99c2b52n%40googlegroups.com.

[Vitaliy L]

Jetty 9.4.x reached the End of Community Support.

https://github.com/eclipse/jetty.project/issues/7958

[Carlos Saltos]

Here a reference commit for an update to Jetty 11 and Servlet API 5 with a Lift fork -> https://github.com/talenteca/olon-web-framework/commit/31cc0dcf91eb7fa4693c2d3166d7a7c39b31bd79

The main changes are at JettyTestServer and HTTPRequestServlet with the new usage of multiparts upload included at Jakarta new Servlets 5.

These changes are still under testing but I hope once stable soon these changes can be included at official Lift new versions.

Best regards,

Carlos Saltos

[Carlos Saltos]

The new Jakarta Servlets 5 are not working for filters so an Apache commons fileupload2 for Jakarta is using now very similar to the original javax old API usage, more info at -> https://github.com/talenteca/olon-web-framework/commit/4e7a7de8059cf8250024957f7f42c7f619a69dfe

[François]

Hello,

We are hit by the problem of lift not supporting Servlet 4/5/etc because we alos use Spring security and they announced end of support for their 5.3 branch, which was the last with the javax.* namespacing.


With the things around lift renewed maintenance, is there a way to publish a 3.6 with the support for servlet 4+ ?

To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/b58aaf44-d3f6-44b5-b143-23ce382d81e6n%40googlegroups.com.

-- 
François ARMAND

[David Pollak]

Please add the requirement to the list Matt put together: https://github.com/orgs/lift/projects/5/views/1

To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/cb416e73-0f38-457b-b4e8-6c67a8c2f950%40gmail.com.

--

Fediverse: https://mastodon.social/@dpp

Lift, the simply functional web framework https://liftweb.net

Blog: https://blog.goodstuff.im

[François]

I don't have the rights for that. Perhaps I should accept the fact that I need to have at least that level of implication :)

To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/CAH6e9LjCCuFztz_rVsSEbnAyemC12J%2B_xz7Bem-vj7%2B0zk%2BxVQ%40mail.gmail.com.

-- 
François ARMAND

[David Pollak]

Maybe Matt can take care of the privileges issue on the issues... ;-)

To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/c9a0f4e0-cb1b-4d51-bbc4-c9b7a30a2756%40gmail.com.

[Matt Farmer]

Oy vey. Githubbbbbbbb. So you should be able to create an issue on the project. Everything in the board is an issue under the hood. In parallel I'll figure out what I need to do to let others contribute to the board itself.

[Matt Farmer]

Looks like I need to add people individually to the board if they're not members of the lift organization -.- 

So let's do this, if you have a Lift 4 thing that gets added, create a new issue on the project and tag me in it and I'll make sure it gets on the board.

[François Armand]

Oh, actually the issue is already there but I didn't see it because the name doesn't talk about servlet version specifically : https://github.com/lift/framework/issues/2008


Perhaps it could be renamed s/Lift 4: update dependencies/Lift 4: update servlet compatibility to servlet 5/ ?

I commented on that issue and also proposed a rationale for a alternative versioning scheme with in summary :
- 3.x: security patch only,
- 4.x: compat to servlet 5 and libs updates and scala 2.13 better compat
- 5.x: Scala 3 only and breaking changes and api evolution

Cheers

[Matt Farmer]

I think honestly at this point I'm inclined to suggest that Lift 4.0 be a major breaking release with all the things we want. I'm kind of afraid if we don't capitalize on the bit of momentum we've got at the moment it's not likely to go anywhere. 😬

[François Armand]

Well, could it be named Lift 5 so that 4 is still available for a non breaking one of some other people like me want [o step up for that?

[Matt Farmer]

I’m not totally opposed to that idea, but it may be the case that we focus on the breaking release first and, if we have motivation, then come back to a bridge release later.

On Aug 16, 2024, at 2:26 AM, François Armand <francoi...@rudder.io> wrote:



Well, could it be named Lift 5 so that 4 is still available for a non breaking one of some other people like me want [o step up for that?

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/liftweb/8f1a4aaa-43a5-4570-ab22-f12e48f5c839%40rudder.io.

[François Armand]

That flies for me, as long as I know that we will be able to have a "lift 4.0 which is just lift 3 with modern servlet version support so that I can use supported spring version", I'm happy

[andreak]

+1

[Matt Farmer]

Alright. I'll do that then.