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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2006-03-01 18:31 ------- If you into the build directory it works, but from anywhere else it doesn't: java -jar file:/var/local/fop-0.91beta/build/fop.jar in my home directory gives: Unable to start FOP: java.lang.RuntimeException: fop.jar not found in directory: /home/werner (or below) at org.apache.fop.cli.Main.getJARList(Main.java:58) at org.apache.fop.cli.Main.startFOPWithDynamicClasspath(Main.java:118) at org.apache.fop.cli.Main.main(Main.java:202) The second problem is that another tool can't refer to fop.jar by putting it in the Class-Path entry of its manifest file. It doesn't matter if you are in the build directory or not. In my opinion the regular extension mechanism should be used. There is nothing static about it. This is a build matter where you keep the manifest file up-to-date when you produce a consistent distribution. -- 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.
