Thanks! I have no strong preference, just preferring to keep it on by default as it generally runs quickly enough; but YMMV if it's slow for someone and impairs quick experimentation I'd be fine to disable it. But obviously we need a switch to turn it off for such cases as the JDK not being compatible.
Sanne On 8 September 2014 12:57, Emmanuel Bernard <emman...@hibernate.org> wrote: > I've push the information to the Asciidoctor folks. > I don't know about any switch though. I guess we do have a way to enable > or disable doc generation but because of various preferences between > project leads, nothing is consistent. > > On Mon 2014-09-08 12:31, Sanne Grinovero wrote: >> On 8 September 2014 12:25, Emmanuel Bernard <emman...@hibernate.org> wrote: >> > On Sun 2014-09-07 14:04, Sanne Grinovero wrote: >> >> - asciidoctor-maven-plugin plugin fails: I'll disable it for now but >> >> it would be great if someone could have a look at it, if it's a JVM >> >> bug we should report it, and otherwise fixing the plugin would be >> >> nice. >> > >> > Can you point me to a URL showing the failure? I can try and contact the >> > relevant persons. >> >> I did debug it, and found that Asciidoctor fails to initialize JRuby: >> the JRuby engine checks which JVM it's being run on to generate >> appropriate opcodes.. and refuses to start on JDK9. >> I guess that's fair enough, so the question would be if there is an >> easy way to disable the asciidoctor-maven-plugin from an environment >> switch, or if we need to mess with Maven profiles. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
