We have a project that creates an executable jar file that bundles jetty, our webapp, hibernate, seam, atomikos transaction essentials, apache derby, activemq and a number of other things.
When I build locally on my machine (CentOS 5.3 x86_64, Sun JDK 1.6.0_13 x86_64) the jar file works fine. When we build on our CI server (CentOS 5.3 x86, Sun JDK 1.5.0_17 x86) the jar file contains a corrupted file. (it's the LICENSE file from woodstox-asl, but I suspect that it's just the position in the jar file. If I try to delete the corrupted file, WinZip will core out (on windows) If I try expanding the jar with jar -xvf, it will expand, but the LICENSE file has incorrect content I'm trying to nail down the issue (let's ignore the other issue I have where the apache camel pom adding dependencies if you are compiling with JDK 1.5) Anyone seen anything like this before... my theories are that it's either a JDK 1.5 thing or a maven-jar-plugin thing -Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
