The release files for fop 1.0 are now ready for review and the release vote.
The release files are built from: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 (created in revision 962495). The release files are found here: http://people.apache.org/~spepping/fop-1_0: cba0264296b49cb3c08f403b19981376 fop-1.0-bin.tar.gz 12312c2f5c17d45000517e32e68e116b fop-1.0-bin.zip bb921758e2eb4327b7ac01c5f5fec455 fop-1.0-src.tar.gz 0ac83532ad1ebfd878ca2a9e43a0a7b9 fop-1.0-src.zip c4d60c28b5a51676ae90473f80808807 fop-1.0-bundle.jar As partially mentioned earlier, I used the following workaround: jdk6: ant distclean, docs jdk14 without junit: ant dist-src, dist-bin (which runs the docs target again), maven-artifacts jdk6: junit This uses the trick that forrest is run each time, but does not clean out its target directory. With jdk14 all junit tests fail. I removed junit from the classpath for jdk14, and ran junit after the build with jdk6. forrest also gives problems with jdk6: 0.95/images/update.jpg: No pipeline matched request: 0.95/images/update.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/fix.jpg: No pipeline matched request: 0.95/images/fix.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/add.jpg: No pipeline matched request: 0.95/images/add.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/update.jpg: No pipeline matched request: 1.0/images/update.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/fix.jpg: No pipeline matched request: 1.0/images/fix.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/add.jpg: No pipeline matched request: 1.0/images/add.jpg at <map:mount> - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 These images are in /images, and the problem does not seem to matter. compliance.pdf: internal-destination or external-destination must be specified in basic-link. As a consequence no compliance.pdf was built. For your perusal I uploaded the build log: build-2010-07-09T16:23:58+02:00.log. Please, review and cast your votes before Wed 14 July 16:00h UTC. +1 from me. Simon -- Simon Pepping home page: http://www.leverkruid.eu
