Closed Vad1mo closed 10 years ago
Sorry for the delay in getting back to you @Vad1mo. I haven't tested Asciidoclet in Java 8 extensively, but it does seem to run for me.
Doclint may complain as it is unaware of the doclet processing that occurs. What error are you getting specifically? What does the end result look like, does it format your xml properly?
This are mainly doclint issues For example: @see http://www.unece.org[UN/EDIFACT] produces warnings. I guess it is not possible to run doclint after asciidoclet? It would be nice to have at least some doclint check.
Getting back to this... finally
Closing for now. Feel free to reopen.
In one of our project, when using the default doclet, we get a bunch of doclint failures, mostly for stuff that's indeed erroneous. When using asciidoclet, we get warnings instead. We don't get the warnings for, say, erroneous html, but we do get them for erroneous @see tags, for example. Is there any way we could control this behavior, i.e have it fail instead of just warn ? Is Javadoc's doclint somewhat reusable for other doclets (does that even make sense ?) I tried -Xdoclint:all but I guess Asciidoclet would need to take into account for it to do anything.
ref: http://docs.oracle.com/javase/8/docs/technotes/tools/unix/javadoc.html#BEJEFABE
Hello, Doclint in jdk 8 is very strict. Switching it of is also not a really good idea.
So the question is: