thanks that worked! Onwards ...
Heiko Seeberger-4 wrote:
>
> Your git stuff was quite OK, the Problem was that the branch is
> 280_port and not vice versa ;-)
>
> Please try it again:
>
> git clone ...
> git branch 280_port origin/280_port
> git checkout 280_port
>
> Heiko
>
> On Sunday, De
Your git stuff was quite OK, the Problem was that the branch is
280_port and not vice versa ;-)
Please try it again:
git clone ...
git branch 280_port origin/280_port
git checkout 280_port
Heiko
On Sunday, December 20, 2009, Channing Walton wrote:
>
> ah I see the problem - I know nothing abou
ah I see the problem - I know nothing about git!
I original thought that the URL at the top of the github page for port_280
would get me port_280 which it doesn't.
I tried following the instructions here:
http://wiki.github.com/bricoleurs/bricolage/working-with-branches
But that isn't working fo
2009/12/20 Channing Walton
>
> ok here it is. The only thing I changed in the main pom is the scala
> version
> to the 2.8.0 beta rc3
>
If you are using the latest version of the 280_port branch there is no need
to change the scala version => It is already 2.8 Beta RC4. Maybe you are
using some
If I skip tests:
[INFO] Compiling 3 source files to
/Users/channing/tmp/280_port/lift-base/lift-actor/target/classes
/Users/channing/tmp/280_port/lift-base/lift-actor/src/main/scala/net/liftweb/actor/LAFuture.scala:19:
error: not found: value common
import common._
^
/Users/channing/tmp/28
ok here it is. The only thing I changed in the main pom is the scala version
to the 2.8.0 beta rc3
[INFO] Compiling 2 source files to
/Users/channing/tmp/280_port/lift-base/lift-common/target/test-classes
error: error while loading Sugar, Scala signature Sugar has wrong version
expected: 5.0
f
2009/12/19 Channing Walton
>
> I would like to use Lift with scala 2.8.0 but need some helping building
> the
> branches. I've checked out the 280_port branch, but when I set the scala
> version to 2.8.0.Beta1-RC3 in the main pom, Lift doesn't compile.
Hmm, the main POM of the 280_port has alre
>
> I could start with 2.7.7 and port it later, but if I can use the 2.8 port,
> and contribute feedback etc, I would like to.
>
Feedback would be great: Very welcome!
280_port should build without failures: Could you please tell me exactly,
what is breaking your build?
Heiko
>
> Channing
> -
bearfeeder wrote:
>
> Do you have a production app that depends on Scala 2.8? Is there a part
> of
> Lift that you immediately need ported to 2.8?
>
No, I don't have an immediate need. However, I am very likely to be starting
on a new app in mid January which will launch in the middle of nex
Do you have a production app that depends on Scala 2.8? Is there a part of
Lift that you immediately need ported to 2.8?
On Sat, Dec 19, 2009 at 1:15 PM, Channing Walton wrote:
>
> I would like to use Lift with scala 2.8.0 but need some helping building
> the
> branches. I've checked out the 280
I would like to use Lift with scala 2.8.0 but need some helping building the
branches. I've checked out the 280_port branch, but when I set the scala
version to 2.8.0.Beta1-RC3 in the main pom, Lift doesn't compile. Either the
specs tests fail because they have the wrong class signature or if I sk
Hi,
I git clone the lift source from git hub. then run mvn install to build it.
It fails with
Downloading:
http://scala-tools.org/repo-releases/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
[INFO] Unable to find resource 'javax.transaction:jta:jar:1.0.1B' in
repository scala-tools.org (http://sc
Hey folks, I'm trying to build the lift sources. It mostly works, but
I see more errors and warnings than I expected. I'm wondering if my
configuration is set up correctly. Or do you see errors/warnings
too? Thx.
mvn jetty:run in liftweb/sites/example seems to work.
I've tried mvn clean, and
13 matches
Mail list logo
