xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38821] New: - The manifest file no longer has a Class-Path entry
Date Wed, 01 Mar 2006 16:54:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38821>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38821

           Summary: The manifest file no longer has a Class-Path entry
           Product: Fop
           Version: 0.91
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: fop-dev@xmlgraphics.apache.org
        ReportedBy: werner.donne@re.be


The manifest file no longer has a Class-Path entry. Why is this? Now it is no
longer possible to run FOP with "java -jar fop.jar" or to launch another
application this way that refers to fop.jar in its manifest file.

Version 0.20.5 did have such an entry, but the error there was that fop.jar
resided in the "build" directory, while the other JARs were in the "lib"
directory. The fop.jar manfest file, however, expected to be a sibling of the
others.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message