DO NOT REPLY [Bug 22581] New: - Incorrect manifest entries in several JAR files

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22581>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22581

Incorrect  manifest entries in several JAR files

           Summary: Incorrect  manifest entries in several JAR files
           Product: Tomcat 5
           Version: 5.0.7
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: drzewo@alpha.net.pl


Many JARs (server/lib/*.jar) contain corrupted manifest files. Some of them are:
 tomcat-jni.jar, jkconfig.jar, jkshm.jar. Class-Path entries seem to be hard
wrapped around seventieth character. 

For example jkshm.jar and tomcat-jni.jar manifest files respectively:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3 
Created-By: 1.4.2-b28 (Sun Microsystems Inc.)
Main-Class: org.apache.jk.common.Shm
Class-Path: tomcat-jk2.jar commons-logging.jar tomcat-util.jar log4j.j
 ar log4j-core.jar

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3 
Created-By: 1.4.2-b28 (Sun Microsystems Inc.)
Main-Class: org.apache.jk.apr.TomcatStarter
Class-Path: ../lib/tomcat.jar log4j.jar log4j-core.jar ../lib/common/l
 og4j.jar ../lib/common/log4j-core.jar ../lib/common/classes ../lib/co
 mmon/commons-logging.jar bootstrap.jar ../server/lib/commons-logging.
 jar ../server/lib/jmx.jar

I also feel that some of the entries are incorrect/redundant, provided that they
are used.