On Nov 19, 12:37 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
But one of the key things to keep in mind regarding Lift is how we as a
community handle problems. One of the biggest, nastiest bugs in Lift-land
crept into the code in the last few
I'm seriously considering Lift for a new project. I know what the
benefits of Scala and Lift are (that's why I'm seriously considering
this as a route forwards :-) What I'm wondering is whether there are
any lurking nasties that I should be aware of (so that I can avoid
learning about them the
Thanks everyone - that's exactly the kind of information that I was
looking for.
Now all I need to do is persuade my colleagues that selecting a young
technology (again) is a good idea ;-)
Thanks again,
paul.butcher-msgCount++
--
You received this message because you are subscribed to the
of this stops me from being able to implement comet
functionality (and Lift is still the best framework I've come across
for this purpose, even without ask/answer). But being able to use ask/
answer would be nice :-)
On Nov 21, 6:27 pm, Paul Butcher [EMAIL PROTECTED] wrote:
So I'm gradually getting my
So I'm gradually getting my head around lift, in particular the comet
support. I'm currently trying to understand how the Chat example's
AskName functionality works. I believe that I've uncovered a bug, but
I'm not sure why it doesn't work or how to fix it.
The Chat class's localSetup method is
I'm sure that I'm missing something very basic here, but I've no idea
what it is. I've downloaded the latest source and run mvn install
successfully. When I try to run mvn site, however, I get the
following:
[WARNING] Unable to process class
On Nov 20, 2:00 pm, David Pollak [EMAIL PROTECTED]
wrote:
When you run out of memory, that's the end of a given job. How much RAM is
in your machine?
As much as will physically fit (3G).
Here's a slightly cut-down version of the end of the Maven output:
[WARNING] Unable to process class
On Nov 20, 2:32 pm, David Pollak [EMAIL PROTECTED]
wrote:
Linux (what distro and version)?
Mac OS X?
Mac OS X 10.5.5 (the latest version).
Paul.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To
On Nov 20, 2:31 pm, David Pollak [EMAIL PROTECTED]
wrote:
I just did a successful build on my Linux machine with 3GB of RAM (I got the
bcel format warning)
Ah - so the error is the out of memory error? The format warning is
just a warning that I don't need to worry about?
Sorry - I had
Disclaimer - I'm a complete Lift newbie, so please forgive any glaring
oversights.
I've been playing around with Lift, and in particular CometActor.
Before trying to write my own, I thought that I'd get the example
Clock actor working. So I created a blank archetype with:
mvn archetype:create
On Nov 17, 4:28 pm, TylerWeir [EMAIL PROTECTED] wrote:
The signature of CometActor changed from 0.9 to 0.10.
Thanks Tyler. I thought that it might be something like that, but when
I checked the latest version of the examples in Git, they were still
using the old style, so I discounted that
On Nov 17, 4:41 pm, David Bernard [EMAIL PROTECTED]
wrote:
maven doesn't pull automatically 0.10-SNAPSHOT if you create a project
with 0.9. Did you change the version of lift into your pom.xml ?
Nope - haven't touched pom.xml. Here's the (I think!) relevant
section:
dependency
12 matches
Mail list logo
