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 interfering with the proper creation of the .war file which may be contributing to the problem. When I try to execute "mvn clean package" without eclipse I get the following error appearing in my surefire-report:
------------------------------------------------------------------------------- Test set: net.genomas.lift.test.AppTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.251 sec <<< FAILURE! testXml(net.genomas.lift.test.AppTest) Time elapsed: 1.228 sec <<< ERROR! java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java: 195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:860) at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:801) at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:726) at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1049) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity (XMLEntityManager.java:1315) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity (XMLEntityManager.java:1282) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource (XMLDTDScannerImpl.java:283) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.dispatch(XMLDocumentScannerImpl.java:1193) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $DTDDriver.next(XMLDocumentScannerImpl.java:1090) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl $PrologDriver.next(XMLDocumentScannerImpl.java:1003) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next (XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl $JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at scala.xml.parsing.FactoryAdapter.loadXML(FactoryAdapter.scala:292) at scala.xml.parsing.NoBindingFactoryAdapter.loadXML (NoBindingFactoryAdapter.scala:60) at scala.xml.XML$.loadFile(XML.scala:42) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:52) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at scala.Iterator$class.foreach(Iterator.scala:414) at scala.runtime.BoxedArray$AnyIterator.foreach(BoxedArray.scala:45) at scala.Iterable$class.foreach(Iterable.scala:256) at scala.runtime.BoxedArray.foreach(BoxedArray.scala:24) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at net.genomas.lift.test.AppTest$$anonfun$wellFormed$1$1.apply (AppTest.scala:48) at scala.Iterator$class.foreach(Iterator.scala:414) at scala.runtime.BoxedArray$AnyIterator.foreach(BoxedArray.scala:45) at scala.Iterable$class.foreach(Iterable.scala:256) at scala.runtime.BoxedArray.foreach(BoxedArray.scala:24) at net.genomas.lift.test.AppTest.wellFormed$1(AppTest.scala:48) at net.genomas.lift.test.AppTest.testXml(AppTest.scala:65) I am working behind a firewall that is important for the security of our data where I work, so it cannot be disabled. I also work behind a proxy but I have configured the maven settings.xml file to get past the proxy, and that definitely works because I am able to download .jar files, etc from the internet when I update to newer versions of scala/lift. I would like to be able to run "mvn clean package" successfully without using eclipse at all to ensure that I am getting a correctly configured .war file. This may be the reason that I am having trouble deploying to Tomcat. Any ideas regarding how to fix this connection failure? Thanks, David On Nov 12, 4:59 pm, David Pollak <feeder.of.the.be...@gmail.com> wrote: > 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 tomcat:run -- does it work? > > Then mvn clean install -- does the WAR file work in Tomcat? > > On Thu, Nov 12, 2009 at 1:10 PM, DavidV <david.v.villa...@gmail.com> wrote: > > > 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: failed LiftFilter: > > java.lang.AbstractMethodError > > > 2009-11-12 16:10:05.834::WARN: failed > > org.mortbay.jetty.plugin.Jetty6PluginWebA > > ppcont...@14c0275{/,C:\Source\trunk\eclipse\testLift\src\main\webapp}: > > java.lang > > .AbstractMethodError > > ... > > > On Nov 12, 3:40 pm, DavidV <david.v.villa...@gmail.com> wrote: > > > 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 onhttp://localhost:8080/portal > > > [INFO] Creating Tomcat server configuration at c:\Source\trunk\eclipse > > > \testLift\ > > > target\tomcat > > > Nov 12, 2009 3:36:51 PM org.apache.catalina.startup.Embedded start > > > INFO: Starting tomcat server > > > Nov 12, 2009 3:36:51 PM org.apache.catalina.core.StandardEngine start > > > INFO: Starting Servlet Engine: Apache Tomcat/6.0.16 > > > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext > > > filterStart > > > SEVERE: Exception starting filterLiftFilter > > > java.lang.AbstractMethodError > > > at scala.actors.Scheduler$.impl(Scheduler.scala:35) > > > at scala.actors.Scheduler$.execute(Scheduler.scala:101) > > > at scala.actors.Actor$class.start(Actor.scala:783) > > > at net.liftweb.http.PointlessActorToWorkAroundBug$.start > > > (LiftServlet.sca > > > la:702) > > > at net.liftweb.http.PointlessActorToWorkAroundBug$.ctor > > > (LiftServlet.scal > > > a:767) > > > at net.liftweb.http.PointlessActorToWorkAroundBug$.<init> > > > (LiftServlet.sc > > > ala:776) > > > at net.liftweb.http.PointlessActorToWorkAroundBug$.<clinit> > > > (LiftServlet. > > > scala) > > > at net.liftweb.http.LiftFilter.init(LiftServlet.scala:563) > > > at org.apache.catalina.core.ApplicationFilterConfig.getFilter > > > (Applicatio > > > nFilterConfig.java:275) > > > at > > > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applica > > > tionFilterConfig.java:397) > > > at org.apache.catalina.core.ApplicationFilterConfig.<init> > > > (ApplicationFi > > > lterConfig.java:108) > > > at org.apache.catalina.core.StandardContext.filterStart > > > (StandardContext. > > > java:3709) > > > at org.apache.catalina.core.StandardContext.start > > > (StandardContext.java:4 > > > 356) > > > at org.apache.catalina.core.ContainerBase.start > > > (ContainerBase.java:1045) > > > > at org.apache.catalina.core.StandardHost.start > > > (StandardHost.java:719) > > > at org.apache.catalina.core.ContainerBase.start > > > (ContainerBase.java:1045) > > > > at org.apache.catalina.core.StandardEngine.start > > > (StandardEngine.java:443 > > > ) > > > at org.apache.catalina.startup.Embedded.start(Embedded.java: > > > 825) > > > at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer > > > (AbstractRunMo > > > jo.java:385) > > > at org.codehaus.mojo.tomcat.AbstractRunMojo.execute > > > (AbstractRunMojo.java > > > :144) > > > at org.apache.maven.plugin.DefaultPluginManager.executeMojo > > > (DefaultPlugi > > > nManager.java:490) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > > > ultLifecycleExecutor.java:694) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > > > Goal(DefaultLifecycleExecutor.java:569) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > > > ltLifecycleExecutor.java:539) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > > > dleFailures(DefaultLifecycleExecutor.java:387) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > > > ts(DefaultLifecycleExecutor.java:348) > > > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > > > (DefaultLi > > > fecycleExecutor.java:180) > > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: > > > 328) > > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: > > > 138) > > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > > > at org.apache.maven.cli.compat.CompatibleMain.main > > > (CompatibleMain.java:6 > > > 0) > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > at sun.reflect.NativeMethodAccessorImpl.invoke > > > (NativeMethodAccessorImpl. > > > java:39) > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke > > > (DelegatingMethodAcces > > > sorImpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:597) > > > at org.codehaus.classworlds.Launcher.launchEnhanced > > > (Launcher.java:315) > > > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > > > at org.codehaus.classworlds.Launcher.mainWithExitCode > > > (Launcher.java:430) > > > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start > > > SEVERE: Error filterStart > > > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start > > > SEVERE: Context [/portal] startupfaileddue to previous errors > > > Nov 12, 2009 3:36:53 PM org.apache.coyote.http11.Http11Protocol init > > > INFO: Initializing Coyote HTTP/1.1 on http-8080 > > > Nov 12, 2009 3:36:54 PM org.apache.coyote.http11.Http11Protocol start > > > INFO: Starting Coyote HTTP/1.1 on http-8080 > > > > This seems more consistent with whatever is happening on the external > > > tomcat server... > > > Thoughts? Also, any ideas about the test failures during the mvn > > > clean package command? > > > > Thanks, I finally feel like I'm getting somewhere now! > > > -David > > > > On Nov 12, 3:21 pm, DavidV <david.v.villa...@gmail.com> wrote: > > > > > 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: > > > > > ------------------------------------------------------- > > > > T E S T S > > > > ------------------------------------------------------- > > > > Running net.genomas.lift.test.AppTest > > > > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.258 > > > > sec <<< FA > > > > ILURE! > > > > > Results : > > > > > Tests in error: > > > > testXml(net.genomas.lift.test.AppTest) > > > > > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 > > > > > [INFO] > > > ------------------------------------------------------------------------ > > > > [ERROR] BUILD FAILURE > > > > [INFO] > > > ------------------------------------------------------------------------ > > > > [INFO] There are test failures. > > > > > Please refer to c:\Source\trunk\eclipse\testLift\target\surefire- > > > > reports for the > > > > individual test results. > > > > [INFO] > > > ------------------------------------------------------------------------ > > > > [INFO] For more information, run Maven with the -e switch > > > > [INFO] > > > ------------------------------------------------------------------------ > > > > [INFO] Total time: 32 seconds > > > > [INFO] Finished at: Thu Nov 12 15:21:06 EST 2009 > > > > [INFO] Final Memory: 29M/53M > > > > [INFO] > > > ------------------------------------------------------------------------ > > > > > I now have Lift-1.0.2 and Scala 2.7.7 and am testing with tomcat. > > > > > On Nov 12, 2:43 pm, David Pollak <feeder.of.the.be...@gmail.com> > > > > wrote: > > > > > > On Thu, Nov 12, 2009 at 11:36 AM, DavidV <david.v.villa...@gmail.com> > > 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 problem? I'll check that out. > > > > > > > I am using Lift 1.0.1 with Scala version 2.7.5 > > > > > > Please use Lift 1.0.2 > > > > > > Please delete ~/.m2 (or whereever your Maven repository is) > > > > > > Please do a "mvn clean install" > > > > > > Then test locally (mvn tomcat:run) If it works, copy to your other > > Tomcat > > > > > instance and see how things work. > > > > > > > It does work with the tomcat on my computer, which leads me to > > believe > > > > > > that it should be compatible with the current versions of > > Lift/Scala > > > > > > that I'm using. Maybe that's an incorrect assumption though, as > > I'm > > > > > > not very familiar with tomcat. > > > > > > > On Nov 12, 2:15 pm, David Pollak <feeder.of.the.be...@gmail.com> > > > > > > wrote: > > > > > > > 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 > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ 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 email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---