fop fails to compile javadocs

[ken@…]

The command

ant javadocs

fails with 100 errors.

I'll attach my log - see lines 162 onwards, particularly from line 260.

The workaround is to omit the 'ant-javadocs', omit 'mv -v build/javadocs .' and omit 'javadocs' from the 'cp -va' command.

This was on LFS-svn-20111124 / BLFS-svn-20111127 x86_64.

[bdubbs@…]

I cannot confirm this problem. I do have the following in my build script:

# Get rid of a bunch of warnings
sed -i -e 's/\xc3\xa9/e/' $(grep -r -l Boris *)
sed -i -e 's/\xc2\xa7//' src/java/org/apache/fop/complexscripts/bidi/DelimitedTextRange.java

I'm using an x86_64 system running lfs-7.6-rc1.

One difference I note is that I'm using JAVA_HOME: /opt/OpenJDK-1.7.0.65-bin and you are using /opt/OpenJDK-1.8.0.25-bin.

I couldn't find anything about jdk-1.8 and fop on google.

[Pierre Labastie]

Sorry for noticing this ticket so late. Before releasing OpenJDK 8, I tested fop. I got the errors Ken has reported, and just removed the generation of the docs from my build, because at first, I was more interested in testing the fop package itself. I was content that I could generate the LFS book in pdf, so I forgot about the javadoc issue. Sorry about that. I confirm the findings of Ken.

Actually, I got also the warnings about "unmappable character for encoding ascii" (related to Boris Pouderous' name), which do not appear in Ken's listing, but seem to have been gotten rid of by Bruce, using sed. Maybe Ken has a better approach (defining encoding or so), which could make its way to the book?

I do not know much about fop nor about javadoc, but let me accept the ticket.

[Pierre Labastie]

Google found that: ​http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html. Looks like the solution is there. I still have to figure out how to pass the -Xdoclint:none option to ant.

[Pierre Labastie]

Actually, Junit is affected by this bug too.

[Pierre Labastie]

Hopefully fixed at r15207