Bug 704298

Rudi, FWIW, I can produce this error too running fop-0.95-5.fc14.noarch.

(In reply to comment #1)
> Rudi, FWIW, I can produce this error too running fop-0.95-5.fc14.noarch.

Strange; works fine for me with 0.95-5 and 1.0-13 on Fedora 14.

Frank, David, can you produce other PDFs with Publican? or is the problem confined to this particular book?

A simple test case if you have nothing else handy:
http://git.fedorahosted.org/git/?p=docs/readme-burning-isos.git

G'day Rudi,


Happens with PDFs of all books on Fed 15 (publican-2.5-2.fc15.noarch) but does not happen when attempted on the same books with Fed 14, so maybe it is something Jeff changed.  I will try to isolate it in one of my books if I have time later (but I am on a training course next week.)


Thanks,

Interestingly, on another less up-to-date rawhide machine, i686 this time,
fop works on the same document sources:

% rpm -qa publican\*  fop\* avalon\* java\* \*pdf\* docbook\* batik\* xalan\* xml\*|sort

avalon-framework-4.1.4-7.fc15.noarch
batik-1.7-9.fc15.noarch
docbook-dtds-1.0-53.fc14.noarch
docbook-style-xsl-1.76.1-1.fc15.noarch
fop-0.95-5.fc14.noarch
java-1.5.0-gcj-1.5.0.0-35.fc15.i686
java-1.6.0-openjdk-1.6.0.0-49.1.9.3.fc15.i686
java_cup-0.11a-5.fc15.noarch
publican-2.5-2.fc16.noarch
publican-fedora-2.0-0.fc15.noarch
xalan-j2-2.7.1-2.fc15.noarch
xml-common-0.6.3-33.fc14.noarch
xml-commons-apis-1.4.01-2.fc15.noarch
xml-commons-resolver-1.2-6.fc15.noarch
xmlgraphics-commons-1.4-1.noarch
xmlrpc-c-1.25.1-1500.svn2077.fc15.i686
xmlrpc-c-client-1.25.1-1500.svn2077.fc15.i686
xmltex-20020625-17.fc15.noarch
xmlto-0.0.23-3.fc13.i686
xmlto-tex-0.0.23-3.fc13.noarch
xmlto-xhtml-0.0.23-3.fc13.noarch

Please note that this bug is blocking f15/f16 systemtap rebuilds in koji:
http://koji.fedoraproject.org/koji/getfile?taskID=3080090&name=build.log
http://koji.fedoraproject.org/koji/getfile?taskID=3080115&name=build.log

It seems like Fedora 15 was released with this bug still unresolved.
At least, I upgraded from Fedora 14, and now fop is entirely broken, i.e. no matter how I invoke it, I get the above "java.lang.NoClassDefFoundError" exception.
(Also, I notice a fop 1.0 version being in testing. When will that be ready ?)

fop-0.95-5.fc14 shipped with Fedora 15 is not compatible with avalon-framework-4.3.

Simple check:

$ fop
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/avalon/framework/configuration/ConfigurationException
	at org.apache.fop.apps.FopFactory.<init>(FopFactory.java:150)
	at org.apache.fop.apps.FopFactory.newInstance(FopFactory.java:166)
	at org.apache.fop.cli.CommandLineOptions.<init>(CommandLineOptions.java:102)
	at org.apache.fop.cli.Main.startFOP(Main.java:153)
	at org.apache.fop.cli.Main.main(Main.java:196)
Caused by: java.lang.ClassNotFoundException: org.apache.avalon.framework.configuration.ConfigurationException
	at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
	... 5 more

$ rpm -q fop
fop-0.95-5.fc14.noarch
$ rpm -q avalon-framework
avalon-framework-4.3-3.fc15.noarch

You can downgrade to avalon-framework-4.1.4 and this error will go away but publican still does not work.

Yes, classes in avalon-framework have changed between 4.2 and 4.3

I'm currently focussing on getting fop 1.0 working for Fedora 15, since as comment #7 notes, there are other problems in 0.95 anyway. :(

(In reply to comment #8)
> Yes, classes in avalon-framework have changed between 4.2 and 4.3

OK, if they lack backward compatibility, is the general Java/Fedora way
to patch all the users?  Or to keep shipping a avalon-4.1 rpm?

(In reply to comment #9)
> (In reply to comment #8)
> > Yes, classes in avalon-framework have changed between 4.2 and 4.3
> 
> OK, if they lack backward compatibility, is the general Java/Fedora way
> to patch all the users?  Or to keep shipping a avalon-4.1 rpm?

Now fixed in fop-1.0-15.fc15, but which now exposes bug 681337 instead :( 

This particular issue, at any rate, is now fixed...

Correction: it's now bug 689930 that's exposed

(In reply to comment #0)
> while running publican/fop.  It aborts the pdf build process.
  :
> org.apache.avalon.framework.configuration.ConfigurationException

I caught same message, when I build X.org modules.
I avoided this message to modify /usr/bin/fop script.

I found this missing class is in /usr/share/java/avalon-framework-api.jar .
So, I added that jar-file to classpath members in /usr/bin/fop as below:
---
[before]
set_classpath commons-io batik-all avalon-framework xmlgraphics-commons \
  commons-logging fop
[after]
set_classpath commons-io batik-all avalon-framework avalon-framework-api xmlgraphics-commons \
  commons-logging fop
---
I don't know whether this method is correct or not.

Thanks,

The update to fop-1.0-16.fc16 from rawhide has fixed the problem with publican on F15.

Can we get the -16 build into Fedora 15 too asap. The -15 build currently submitted as an update for F15 is broken due to missing event-model.xml files.

fop-1.0-17.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/fop-1.0-17.fc15

Package fop-1.0-17.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fop-1.0-17.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/fop-1.0-17.fc15
then log in and leave karma (feedback).

fop-1.0-17.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.