I updated the build artifacts in http://people.apache.org/~spepping/. These would be identical to the release artifacts if I would tag the branch now.
Simon On Wed, Jun 30, 2010 at 03:43:00PM +0200, Simon Pepping wrote: > I have been able to circumvent the reported problem by using ant > 1.7. A new problem appeared: With jdk14 forrest fails to generate > changes.html, changes.rss and changes.pdf. It may be that the plugin > input.projectInfo does not work well with jdk14. > > I used the following workaround: > jdk14: ant distclean > jdk6: ant docs > jdk14: dist-src > jdk14: dist-bin, which runs the docs target again > jdk14: maven-artifacts > > This uses the trick that forrest is run each time, but does not clean > out its target directory. > > In order that you can check for yourself that this trick produces a > correct build, I have uploaded the build artifacts to > http://people.apache.org/~spepping/. I added my signature to the KEYS > file in the branch only after this build, so you can only find it in > subversion, or in the fop KEYS file. > > I will now proceed to merge recent trunk change sets into the branch, > tag and build the final artifacts. > > Simon -- Simon Pepping home page: http://www.leverkruid.eu --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
