[hibernate-dev] OGM: fixing the build on Java8

[Steve Ebersole]

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 <emmanuel at hibernate.org>wrote:

> +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 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 fix all javadocs, but then we'd still be
> > having aggressive checks in the future..
> > Considering the complaints about checkstyle, I'm not sure we want that.
> >
> > For the moment, I've reconfigured the OGM Jenkins job running on Java8
> to use
> >
> >     -Dmaven.javadoc.skip=true
> >
> > -- Sanne
> >
> > [1]
> https://github.com/Sanne/hibernate-ogm/commit/6b83af5ad3926e7bb134bf85e0d205d126867fdc
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>