Hi, I think the best way to track this is to file a JIRA ticket on http://jira.codehaus.org/browse/MJAVADOC
Btw, we might be interested by https://github.com/AdoptOpenJDK/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java Cheers 2013/6/19 sebb <seb...@gmail.com> > I expect you have all see the news about the Javadoc javascript bug. > > It's going to take a long time for everyone to update their Java > installations to Java 1.7 u25. Likewise for builds that need to use > other Java versions, tweaking poms so Java 7 is used for Javadocs > whilst still maintaining compatibility is a non-trivial task. > > Is there any interest in releasing a "quick-fix" version of the > javadoc plugin that automatically runs the tool after Javadoc > completes? > > The fix code is in Java, and can easily be directly called from the > plugin (no need to start a new process). > > The license looks friendly so long as the code is only used for > Javadoc fixups, and changes are allowed, which is just as well - > > There are a couple of bugs in the tool as currently released. > It does not close all the resources; and failure to close the input > file means it cannot delete the original input file on Windows; that > needs to be fixed as it would not make sense to keep the old faulty > file (even if it is now called index.html.orig). > > I can provide details of the fixes, but a decent IDE will probably > warn about them anyway. > > It would be a great service to the Java community if this could be > fast-tracked. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
