20 12 2006

If you find that you get a invalid  header field with a Maven 2 pacakaged war or jar then you are probably using and old version of the maven-archiver plugin that cant cope with pom descriptions containing line breaks.

This may be in the war, but it could also be any of the jars (including 3rd party jars) included in the  war.
There is a simple solution, remove the .m2/repository/org/apache folder and let mvn pull uptodate versions from the remote repositories.

Dec 18, 2006 8:35:44 PM org.apache.catalina.core.StandardContext
start SEVERE: Error in dependencyCheck
java.io.IOException: invalid header field
at java.util.jar.Attributes.read(Attributes.java:389)
at java.util.jar.Manifest.read(Manifest.java:167)
at java.util.jar.JarInputStream.(JarInputStream.java:66)
at java.util.jar.JarInputStream.(JarInputStream.java:43)
at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:372)
at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:183)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4035)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)

Advertisements

Actions

Information




%d bloggers like this: