Ok, after some more digging, I can reproduce on Linux/Ubuntu and I understand the issue now (a file is added as a directory in the archive). I should have a fix by end of today.
alex On Sun, Oct 10, 2010 at 10:40 AM, Alex Boisvert <[email protected]>wrote: > I can't reproduce on Linux/Ubuntu so I'm suspecting something to do with > the platform (Windows). I'll give it a go on a Windows machine later > today. > > aelx > > > On Sun, Oct 10, 2010 at 10:08 AM, Ara Vartanian <[email protected] > > wrote: > >> I'm having an unusual error that I was hoping someone could shed some >> insight on. I've attached a very simple skeleton project that packages >> a war and also a stack trace of the error. I'm trying to deploy this >> war using buildr's jetty integration. The exception I'm receiving on >> running: >> >> buildr foo3:jetty >> >> is: >> >> 247 [btpool0-1] WARN org.mortbay.log - Failed startup of context >> org.mortbay.jetty.webapp.webappcont...@36b29562 >> {,jar:file:/C:/Users/Ara/scala/foo3/target/foo3-1.0.0.war!/} >> java.util.zip.ZipException: invalid entry compressed size (expected 0 >> but got 2 bytes) >> >> And the war fails to properly load. What makes this interesting is >> (and why I think it might be related to buildr rather than jetty) is >> that the minimal difference that distinguishes between a successful >> startup and an exception is placing *any file whatsoever* in the >> src/main/resources folder. So, for example, I have in the >> src/main/resources folder of skeleton project a single file some_file. >> Deleting that file (and doing a clean build) removes the exception. >> >> Any insight on this would be greatly appreciated. >> >> -- Ara Vartanian >> > >
