Update:
The tomcat incompatability with the external server was caused by a
Java version mismatch. I was compiling my scala code with a newer
version of the JDK. I had an older JDK installed on the external
server and this was causing a problem with some of my class files (but
not others, oddly).
If you call maven with the right parameter it will skip the tests. I think it's
something like -Dmaven.tests.skip .
-
DavidV wrote:
More specifically, I am trying to follow the stack trace to lead me to
some sort of URL so that I can see where and why this con
Just delete the AppTest.scala file.
On Tue, Nov 17, 2009 at 7:41 AM, DavidV wrote:
> More specifically, I am trying to follow the stack trace to lead me to
> some sort of URL so that I can see where and why this connection is
> trying to be made. I'm not sure why the AppTest needs to make a
> c
I skipped the Test portion of mvn package by removing the testCompile
goal from my pom file under the maven-scala-plugin. War packaging is
now working correctly, but the webapp still isn't deploying on the
remote Tomcat server...will keep at it and will post my solution if I
find one... I think i
More specifically, I am trying to follow the stack trace to lead me to
some sort of URL so that I can see where and why this connection is
trying to be made. I'm not sure why the AppTest needs to make a
connection in the first place. Can I just skip the Test portion of
the mvn package command? O
For the time being I have code that compiles correctly and I am
leaving eclipse completely out of the picture. I am running Windows
Vista 64bit. I have quit eclipse and tried to run a "mvn clean
install" to rebuild my project, but I get the exact same error that I
previously posted (ConnectExcept
On Fri, Nov 13, 2009 at 9:15 AM, DavidV wrote:
>
> When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run
> my code through maven. However, I am concerned about my inability to
> run the "mvn clean package" command successfully without first running
> the "clean" command in eclipse
When running Lift-1.0.2 and Scala-2.7.5 I am able to compile and run
my code through maven. However, I am concerned about my inability to
run the "mvn clean package" command successfully without first running
the "clean" command in eclipse. I am afraid that this extra eclipse
step may be interfe
Scala is very, very, super ultra mega version fragile. This means that code
compiled with 2.7.5 will not work with code compiled with 2.7.7 and vice
versa.
So, in your pom.xml file, please set your scala version to 2.7.5 (nothing
else... not 2.7.4, not 2.7.7) and lift to 1.0.2
Then mvn clean tom
Another potentially helpful detail is that I get the same liftFilter
error when running on a local jetty server through maven as I do when
running on tomcat (also through maven). I am executing a clean
command before running the web app each and every time.
...
2009-11-12 16:10:05.833::WARN: fa
I just tried to run the same code that used to work with Lift-1.0.1
and Scala 2.7.5 with my updates to Lift 1.0.1 and Scala 2.7.7 and I
got the following error:
[INFO] [tomcat:run {execution: default-cli}]
[INFO] Running war on http://localhost:8080/portal
[INFO] Creating Tomcat server configurat
On a side note, while I'm installing Lift 1.0.2 with Scala2.7.5, I
always execute a "clean" command before the mvn package. However, I
also need to execute a "clean" in eclipse before the mvn package works
properly. Otherwise, I get this error:
--
On Thu, Nov 12, 2009 at 11:36 AM, DavidV wrote:
>
> I don't appear to have any conflicting jars in my TOMCAT_HOME/common/
> lib folder, however, I am now realizing that I have a postgres
> jdbc3 .jar file in there and I am using a jdbc4 .jar postres file in
> my webapp. Perhaps that is the probl
I don't appear to have any conflicting jars in my TOMCAT_HOME/common/
lib folder, however, I am now realizing that I have a postgres
jdbc3 .jar file in there and I am using a jdbc4 .jar postres file in
my webapp. Perhaps that is the problem? I'll check that out.
I am using Lift 1.0.1 with Scala
What version of Lift are you using?
If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got the Scala
version set to 2.7.7
If you're using Eclipse for development, please make sure to do a mvn *clean
* package to build your WAR file. The clean phase is super important.
On Thu, Nov 12,
Have you got any conflicting jars in TOMCAT_HOME/lib ?
--~--~-~--~~~---~--~~
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 this group, send e
16 matches
Mail list logo
