You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The widgets source code is no longer compatible with Lift 2.6. I don't think this is a problem. I propose to modify the build.sbt to specify Lift 3.0-SNAPSHOT.
When compiling with Lift 2.6 the error is:
[info] Compiling 25 Scala sources to /Users/richard/Developer/lift/modules/widgets/target/scala-2.11/classes...
[error] /Users/richard/Developer/lift/modules/widgets/src/main/scala/net/liftmodules/widgets/autocomplete/AutoComplete.scala:181: value liftPath is not a member of object net.liftweb.http.LiftRules
[error] val what: String = encodeURL(S.contextPath + "/" + LiftRules.liftPath + "/ajax/"+ S.renderVersion+"?"+func+"=foo")
[error] ^
and
[error] /Users/richard/Developer/lift/modules/widgets/src/main/scala/net/liftmodules/widgets/tree/TreeView.scala:120: value liftPath is not a member of object net.liftweb.http.LiftRules
[error] "/"+LiftRules.liftPath + "/ajax/"+ S.renderVersion)+"?"+key+"=_"
[error] ^
[warn] three warnings found
[error] two errors found
There are also deprecation warnings about deprecations to @deprecations. Which is my all time favourite deprecation.
The text was updated successfully, but these errors were encountered:
I haven't checked if this is already the case, but I would say do a build for lift 2.6 scala 2.11 and then bump the widgets to 1.4-SNAPSHOT and have it only build for 2.11 and lift 3.0-SNAPSHOT
It looks like I didn't publish 2.6 (non-snapshot) versions of the modules when 2.6 came out. So I'll do that before anything else; and then bump the version number up and switch to 3.0-SNAPSHOT.
The widgets source code is no longer compatible with Lift 2.6. I don't think this is a problem. I propose to modify the build.sbt to specify Lift 3.0-SNAPSHOT.
When compiling with Lift 2.6 the error is:
and
There are also deprecation warnings about deprecations to
@deprecations
. Which is my all time favourite deprecation.The text was updated successfully, but these errors were encountered: