Steve, there is a reference to org.hibernate.engine.Mapping in a non-javadoc comment with a javadoc tag ("@see"): org.hibernate.spatial.dialect.oracle.SDOObjectProperty#getReturnType Also: org.hibernate.spatial.dialect.oracle.SDOObjectMethod#getReturnType Maybe you could try removing/fixing this comment and see how it goes? The bug may be about the javadoc processor trying to process non-javadoc comments whenever it sees a javadoc tag... Which could be worked around easily.
Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 2 January 2018 at 20:15, Steve Ebersole <st...@hibernate.org> wrote: > Sanne, have you had a chance to look at this? If not, I may have to just > disable Java 9 from Travis > > On Wed, Dec 27, 2017 at 8:37 PM Steve Ebersole <st...@hibernate.org> > wrote: > > > I worked on getting Travis CI set up on ORM for reasons discussed here > > previously. But I am running into a really strange error when I enabled > > Java 9: > > > > javadoc: error - An exception occurred while building a component: > > ClassSerializedForm > > (com.sun.tools.javac.code.Symbol$CompletionFailure: class file for > > org.hibernate.engine.Mapping not found) > > Please file a bug against the javadoc tool via the Java bug reporting > page > > (http://bugreport.java.com) after checking the Bug Database ( > > http://bugs.java.com) > > for duplicates. Include error messages and the following diagnostic in > > your report. Thank you. > > com.sun.tools.javac.code.Symbol$CompletionFailure: class file for > > org.hibernate.engine.Mapping not found > > > > It seems like javadoc is complaining because it sees a reference to a > > class (org.hibernate.engine.Mapping) that it cannot find. It is true > that > > there is no class named org.hibernate.engine.Mapping, the real name is > > org.hibernate.engine.spi.Mapping - but what is strange is that I search > the > > entire ORM project and found zero references to the String > > org.hibernate.engine.Mapping. > > > > I just kicked off a run of the ORM / Java 9 Jenkins job to see if it has > > the same failure. > > > > Anyone have any ideas? > > > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev