Is this working now? And how about Google Appengine Integration?
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from
On Thu, May 7, 2009 at 4:46 AM, Tom t0m4rn...@gmail.com wrote:
Is this working now?
Which this are you referring to?
And how about Google Appengine Integration?
GAE works except for Comet related stuff which will not work until Google
supports some sort of message queue system.
On Thu, May 7, 2009 at 3:00 PM, Tom Arnold t0m4rn...@gmail.com wrote:
On Thu, May 7, 2009 at 6:13 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Which this are you referring to?
Oh sorry. I meant the Lift-Scala-Eclipse integration. (+GAE)
I tried to get it working, but even
On Thu, May 7, 2009 at 11:31 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
If you've got questions about Scala and Eclipse and GAE generically, this is
not the best place to ask them.
He wants to get Lift + maven + the Scala IDE for Eclipse + the GAE
plugin for Eclipse all working
On Thu, May 7, 2009 at 3:42 PM, Miles Sabin mi...@milessabin.com wrote:
On Thu, May 7, 2009 at 11:31 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
If you've got questions about Scala and Eclipse and GAE generically, this
is
not the best place to ask them.
He wants to get Lift +
On Thu, May 7, 2009 at 11:43 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
I'm totally cool with you providing support for this configuration on this
list.
Well, hang on ...
The point is that this is all of our problem ... I can help with
generic Scala IDE problems, but Lift + Maven +
Hi,
On Fri, May 8, 2009 at 7:48 AM, Miles Sabin mi...@milessabin.com wrote:
The point is that this is all of our problem ... I can help with
generic Scala IDE problems, but Lift + Maven + GAE plugin stuff is not
in my purview.
As for Lift + Maven + GAE/J, the following may be helpful,
Can we fix our existing Lift project poms by adding the lump of xml
you just posted, or will that break things?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to
Quick note :
* You need to use build-helper-maven-plugin (like Josh shown) only for mixed
project.
* if you set in your
build
sourceDirectorysrc/main/scala/sourceDirectory
testSourceDirectorysrc/test/scala/testSourceDirectory
then the maven-eclipse-plugin use the right directory
Good catch!
Also if you just place your scala files in src/main/java (with your java
files) you would be ok.
On Wed, Apr 29, 2009 at 8:55 AM, David Bernard
david.bernard...@gmail.comwrote:
Quick note :
* You need to use build-helper-maven-plugin (like Josh shown) only for
mixed project.
*
On Apr 29, 1:55 pm, David Bernard david.bernard...@gmail.com wrote:
* if you set in your
build
sourceDirectorysrc/main/scala/sourceDirectory
testSourceDirectorysrc/test/scala/testSourceDirectory
I seem to have that already but still have the problem after doing mvn
has this already been applied to the pom?
should it work now?
thanks alot,
kai
On Apr 22, 4:11 pm, Josh Suereth joshua.suer...@gmail.com wrote:
On Wed, Apr 22, 2009 at 8:53 AM, Miles Sabin mi...@milessabin.com wrote:
On Wed, Apr 22, 2009 at 1:16 PM, Josh Suereth joshua.suer...@gmail.com
I've just set up a lift project in eclipse, here are the versions:
Eclipse Version: 3.5.0 Build id: I20090416-1053
Scala plugin 2.7.4RC1
The steps I went through are as follows:
1. created the lift project somewhere with mvn as usual
2. ran mvn:eclipse:eclipse on the created project
3.
On Wed, Apr 22, 2009 at 8:05 AM, Miles Sabin mi...@milessabin.com wrote:
On Wed, Apr 22, 2009 at 11:14 AM, Channing channingwal...@mac.com wrote:
4. went to the project properties and edited each of the source
folders removing the 'Excluded items' which was preventing eclipse
from
On Wed, Apr 22, 2009 at 11:14 AM, Channing channingwal...@mac.com wrote:
4. went to the project properties and edited each of the source
folders removing the 'Excluded items' which was preventing eclipse
from compiling the scala code
snip/
Whenever I change the pom, I use a terminal to run
On Wed, Apr 22, 2009 at 1:16 PM, Josh Suereth joshua.suer...@gmail.com wrote:
The maven-eclipse-plugin is currently broken in the sense that it won't
pay attention to the source directories configured by the maven-scala-plugin.
The developers seem unwilling to try to integrate these two
On Wed, Apr 22, 2009 at 8:53 AM, Miles Sabin mi...@milessabin.com wrote:
On Wed, Apr 22, 2009 at 1:16 PM, Josh Suereth joshua.suer...@gmail.com
wrote:
The maven-eclipse-plugin is currently broken in the sense that it won't
pay attention to the source directories configured by the
Since Scala is a dialect of Java, and Lift is an extension of that, I
went the Netbeans route because NB is basically part of Java, and I am
happy so far:
- Netbeans is quicker to load than Eclipse, and doesn't create all
those zillions of files behind;
- Netbeams handles all the moving parts
I've played a bit with both netbeans 6.7m2 and eclipse 3.4.2 with the 2.7.3
plugin. I'm currently using eclipse, but I've found it to be fairly
tempermental... I often have to manually do a clean build to get correct
error messages, or reload the file in the editor, and stepping through the
Eclipse has been on and off with me. The new version definitely works
better, but I write code against Maven projects with nested modules and that
combination seems to make everything fairly unhappy. I get weird error
messages like _root_ does not exist that go away if I stop and restart
Eclipse.
The main one i've come across is that whole jetty WebAppContext which
I dont seem to be able to get rid of did anyone find a solution
for that?
Cheers, Tim
On Apr 21, 8:45 pm, Derek Chen-Becker dchenbec...@gmail.com wrote:
Eclipse has been on and off with me. The new version definitely
On Tue, Apr 21, 2009 at 8:45 PM, Derek Chen-Becker
dchenbec...@gmail.com wrote:
Eclipse has been on and off with me. The new version definitely works
better, but I write code against Maven projects with nested modules and that
combination seems to make everything fairly unhappy. I get weird
I wrote:
I'm going to be doing on Lift development with Eclipse at the Scala
Lift Off
Let me try that again ...
I'm going to be doing a presentation on Lift development with Eclipse
at the Scala Lift Off.
Cheers,
Miles
--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
First off, I don't want to come off as whining. I know you've put some
tremendous effort into this and it shows. The new version (I'm actually
using 2.8.0_blahblah), especially the new JDT weaving makes things generally
a pleasure. The weird part for me is that with nested modules it sometimes
On Tue, Apr 21, 2009 at 9:10 PM, Derek Chen-Becker
dchenbec...@gmail.com wrote:
First off, I don't want to come off as whining. I know you've put some
tremendous effort into this and it shows. The new version (I'm actually
using 2.8.0_blahblah), especially the new JDT weaving makes things
sorry for taking over this thread again...
I tried NetBeans and it does not work any better. No JavaDocs, no
Sources, nothing. I tried to download all sources/javadocs menu-
item, etc about a dozen times..
I even got maven to work via runProject but of course there seems no
way to enable
I'll open a ticket in Trac for the errors I'm seeing. I'm actually getting a
different error now: Build compiler (scalac) crashed. I'm happy to open
tickets but I'm never sure if I'm duping :(. For what it's worth I'm getting
a similar error to what I was getting earlier in a project that is a
On Wed, Apr 22, 2009 at 12:31 AM, Derek Chen-Becker
dchenbec...@gmail.com wrote:
I'll open a ticket in Trac for the errors I'm seeing. I'm actually getting a
different error now: Build compiler (scalac) crashed.
That would typically (tho' not invariably) suggest a scalac bug which
can be
Generally, yes, but I'll confirm the next time I get the error.
Thanks,
Derek
On Tue, Apr 21, 2009 at 5:35 PM, Miles Sabin mi...@milessabin.com wrote:
On Wed, Apr 22, 2009 at 12:31 AM, Derek Chen-Becker
dchenbec...@gmail.com wrote:
I'll open a ticket in Trac for the errors I'm seeing. I'm
I've seen that problem, though I don't recall exactly when. Perhaps your
your classpath variables aren't set up correctly?
With your project highlighted in the project explorer, try the following
menu sequence: Project Properties Java Build Path Libraries.
On my version, I see a bunch of
30 matches
Mail list logo
