Moving forward on Lift 4

[Matt Farmer]

Hey all - it's been a minute.

Life got busy again there for a bit, but I'm looking at trying to get Lift 4.0 out the door as a stepping stone release. I'm not going to be including a ton of major changes here, but now I've got CI/CD working in GitHub Actions and we're building on the most recent Scala 2.13 build. Consider this a final call for anything folks want to see included in the release.

Cheers,

Matt

[François]

Seems to be good for me. 

We have now more feedbacks on "lift 4 with scala 3" since we were able to update Rudder to scala 3 with liftweb 4.0.0-M1/scala 2. 

The most annoying bit was the old version of scala-parser that forced us to create a different backend for cron4s to avoid incompatibilities.

But with that, we have working Rudder in scala 3. 

-- 
François ARMAND

[lin qing]

It's good if lift4 upgrade the scala-xml 1.3 to 2.0+.  

[sfcheb]

its so important to get liftweb working with scala 3. is the plan for lift 4 to support it?

[Matt Farmer]

Yes. I’m planning for Lift 4 to support 2.13 and 3.3.6 and Lift 5 to support Scala 3 LTS and latest. 

I’ve got common, actor, and markdown building for Scala 3. Working on json now. 

On Aug 30, 2025, at 11:11 PM, sfcheb <ksa...@gmail.com> wrote:

its so important to get liftweb working with scala 3. is the plan for lift 4 to support it?

--
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 visit https://groups.google.com/d/msgid/liftweb/88072bdb-147e-47ed-ba58-3d7f5b126556n%40googlegroups.com.

[Andreas Joseph Krogh]

While moving towards Lift 4 I think we should update some more libs, for example:

• commons-fileupload2-jakarta-servlet6 2.0.0-M4
• jakarta.mail-api 2.1.4
• scala-xml 2.3.0 (maybe 2.4.0, haven't tried it)
• jakarta.servlet-api 6.1.0
• jakarta.persistence-api 3.2.0
• joda-time 2.14.0
• joda-convert 2.2.0

We use these version in our custom Lift-4 build (which works well with jakarta.*-namespace).

 

I'd also suggest the following changse to LiftRules:

@volatile var liftContextRelativePath: () => List[String] = () => List("lift")

@volatile var pageJsFunc: () => List[String] = () => liftContextRelativePath() :+ “page”

Note that this is a breaking change, but IMO much needed to better control where Lift lives, which makes it easier to co-exist with other frameworks.

I can make the above changes if you agree.

 

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

and...@visena.com

www.visena.com

To view this discussion visit https://groups.google.com/d/msgid/liftweb/57536FBD-C8F6-478D-8BF1-7B5D49992565%40frmr.me.
 

 

 

[lin qing]

It's great that you could contribute back your customization, I wait for it for many years.

You received this message because you are subscribed to a topic in the Google Groups "Lift" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/liftweb/XcGmAwBS-ZA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to liftweb+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/liftweb/VisenaEmail.17.ef9b4350876ec9d6.1990490020c%40origo-test01.app.internal.visena.net.