I got the same problem. Where did you put your downloaded tomcat zip?
Thanks. On 1/29/07, Caoilte O'Connor <[EMAIL PROTECTED]> wrote:
Okay. Hmm. I'm not sure how I fixed it, but I did. Or at least the problem went away when I downloaded the tomcat zip myself for cargo, let it run with that and deleted it afterwarsd. Similarly I was having integration test failures because it kept trying to create users with the same primary key id, but that went away when I ran "mvn" instead of "mvn integration-test". But I have it all working now. And the source in place and ready to mess with. The only confusing part of the wiki so far was for putting core source files in place in a multi modular proeject (like I'm playing with), http://appfuse.org/display/APF/AppFuse+Core+Classes It's not explicitly clear which POM should have the AppFuse Data Common Package excluded. I could only find it in the WEB module. Otherwise great work so far. I look forward to M3. c On 28/01/07, Caoilte O'Connor <[EMAIL PROTECTED]> wrote: > Hi, > I'm just starting out with Appfuse2 so I'll probably be posting a lot > of queries for a while. > > Alas, right now I can't even get the integration tests to finish. I > get this error, > > [INFO] [cargo:start {execution: start-container}] > [INFO] ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Error while expanding /tmp/cargo/installs/apache- tomcat-5.5.17.zip > Unexpected end of ZLIB input stream > [INFO] ------------------------------------------------------------------------ > [INFO] Trace > Error while expanding /tmp/cargo/installs/apache-tomcat-5.5.17.zip > at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java :164) > > > I did a couple of projects porting appfuse1 to maven1 back in the day > so it occured to me a couple of files might not have downloaded > properly. I tried completely regenerating my .m2 repositary. It didn't > help. There are lots of snapshots in the dependency graph. Has one > (Cargo?) gone awry very recently? > > Also, is there anyway to stop maven automatically checking for new > versions of every SNAPSHOT jar every last single time it's run? I > forsee it being quite annoying. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Regards, Cuong Hoang
