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] - The manifest file no longer has a Class-Path entry
Date Thu, 02 Mar 2006 13:27:53 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





------- Additional Comments From jeremias@apache.org  2006-03-02 14:27 -------
That's exactly why I don't like the Class-Path entry. You have to specify a
definitive location for the JARs. When you deploy an application you normally
don't care about the setup in the development environment. You simply pack the
necessary JARs together. That's why I'm strongly for leaving the Class-Path
entry like it is right now and that you copy fop.jar over into the lib
directory. Otherwise next time, someone else comes and says: Why do I have to
place fop.jar in a different location that the other JARs? The alternative you
have is to create a simple Ant script that will patch fop.jar's manifest exactly
the way you want it.

-- 
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