Got also got a bunch of failures in HV with JDK8. Luckily a big part seems to
be
related to author tags of the form:
@author name
I’ll fix this and the remaining issues up shortly. I never likes this form of
author syntax, especially
since it was not valid HMTL ;-)
Funny enough, we discusse
Sorry, I see it now in the blog you linked.
On Mon, Feb 24, 2014 at 7:40 AM, Steve Ebersole wrote:
> Strict in what sense? I have played with using the asciidoc javadoc
> doclet support (mainly to make it easier to use annotations in code
> samples). Do you have any specific info on this new
Strict in what sense? I have played with using the asciidoc javadoc doclet
support (mainly to make it easier to use annotations in code samples). Do
you have any specific info on this new strictness?
On Mon, Feb 24, 2014 at 7:22 AM, Emmanuel Bernard wrote:
> +1 for the commit as a first stage
+1 for the commit as a first stage and then open a JIRA for a JavaDoc
cleanup. Though the no self-closed HTML tag is beyond me.
Emmanuel
On Sat 2014-02-22 23:32, Sanne Grinovero wrote:
> It turns out OGM isn't building on Java8 because of some new very
> strict checks being performed on javadoc s
Thanks for having a look into this.
I'd prefer if we fixed the JavaDoc issues, at least for those types which
we consider API/SPI. There is
https://hibernate.atlassian.net/browse/OGM-331for fixing JavaDoc
issues such as broken links etc.
--Gunnar
2014/2/23 Sanne Grinovero
> It turns out OGM
It turns out OGM isn't building on Java8 because of some new very
strict checks being performed on javadoc syntax:
http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html
The quick fix is to disable it.. if we opt for that this change [1] is
what you need.
A better fix would be to f
