Hi,
http://stackoverflow.com/questions/3057841/too-long-line-in-manifest-file-while-trying-to-create-jar
http://stackoverflow.com/questions/7402271/maven-archiver-putting-in-weird-line-breaks-in-classpath-for-manifest
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719094
https://bugs.eclipse.org/bugs/show_bug.cgi?id=91309
Did you try with Maven 3.3.3, JDK 7u79, maven-jar-plugin 2.6,
maven-war-plugin 2.6 ?
https://issues.apache.org/jira/browse/TAP5/fixforversion/12324358/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
5.3.8
Le 12/05/2015 17:29, Daniel Jue a écrit :
Hi, I recently ran into this "problem" that causes my module to not
auto-load, and in fact prevents the Tomcat server from starting my T5 war
file.
The error starts with
Exception loading module(s) from manifest
jar:file:/path-to-jar-file-in-web-inf-lib/MANIFEST.MF: Failure loading
Tapestry IoC module class:
stack trace starts at IOCUtilities.java:123
The culprit was that the MANIFEST.MF can't have lines longer than 72
characters, and if it is longer it [Maven] will wrap on the next line
including an additional space. The total of my manifest is right at 72,
but it wrapped it at 70 characters anyway. This is strange since I didn't
have problems with it last week.
The relevant lines of my manifest.mf for the pluggable module looks like
this:
Tapestry-Module-Classes: graphene.augment.mitie.web.services.MITIEModu
le
I'm using Maven 3.0.4, Tapestry 5.3.7, Jdk 1.7.0
I'm not sure if Tapestry could be made to take that into account and
coalesce the Strings.
I did discover it's part of the Java spec though:
http://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#Notes_on_Manifest_and_Signature_Files
