The title of this Jira was inaccurate, I changed it to be a general blanket fixes for getting Java 9 to work for uimaj.
The first issue (re @generated tags, not annotations) was caused by the javadoc maven plugin failing to parse the java version number because it is a bit unusual. Fixed by a) upgrading to a later javadocs maven plugin version and b) specifying directly the javadoc version wanted. Next issue was the javadoc lint checker seems even more strict - it's complaining if you close a <p> tag with a </p>. There's lots of these, so I'm going to try and debug this a bit to see what all the strange rules they may have for html formatting. If anyone has pointers to these, please reply; I didn't see in a short web search. -Marshall On 3/13/2017 5:38 PM, Marshall Schor (JIRA) wrote: > Marshall Schor created UIMA-5369: > ------------------------------------ > > Summary: java9 javadoc requires defs for annotations > Key: UIMA-5369 > URL: https://issues.apache.org/jira/browse/UIMA-5369 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework > Reporter: Marshall Schor > Assignee: Marshall Schor > Priority: Minor > Fix For: 2.10.0SDK, 3.0.0SDK-beta > > > JCas classes have annotations like @generated in them. The Java 9 javadoc > processor complains if these are not defined in the classpath. This happens > in the final uimaj project when the aggregate javadoc is built. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.15#6346) >
