Steve Lawrence created DAFFODIL-2111:
----------------------------------------
Summary: JavaDoc errors on Java 11
Key: DAFFODIL-2111
URL: https://issues.apache.org/jira/browse/DAFFODIL-2111
Project: Daffodil
Issue Type: Bug
Components: API, Documentation
Environment: JDK: oraclejdk11 Scala: 2.11.12
Reporter: Steve Lawrence
Fix For: 2.4.0
During a TravisCI build on Java 11, I noticed the following error output
related to building JavaDocs with {{sbt daffodil-japi/genjavadoc:doc}}:
{code:java}
[error] Loading source file
/home/travis/build/apache/incubator-daffodil/daffodil-japi/target/java/org/apache/daffodil/japi/ParseResult.java...
[error]
/home/travis/build/apache/incubator-daffodil/daffodil-japi/target/java/org/apache/daffodil/japi/ParseResult.java:35:1:
error: illegal start of type
[error] *
[error] ^
[error]
/home/travis/build/apache/incubator-daffodil/daffodil-japi/target/java/org/apache/daffodil/japi/ParseResult.java:36:1:
error: <identifier> expected
[error] * @deprecated Use parse(ReadableByteChannel, InfosetInputter) to parse
the data and get the infoset representation from the InfosetOutputter. Since
2.0.0.
[error] ^
[error]
/home/travis/build/apache/incubator-daffodil/daffodil-japi/target/java/org/apache/daffodil/japi/ParseResult.java:36:1:
error: <identifier> expected
[error] * @deprecated Use parse(ReadableByteChannel, InfosetInputter) to parse
the data and get the infoset representation from the InfosetOutputter. Since
2.0.0.
[error] ^
[error]
/home/travis/build/apache/incubator-daffodil/daffodil-japi/target/java/org/apache/daffodil/japi/ParseResult.java:36:1:
error: ';' expected
[error] * @deprecated Use parse(ReadableByteChannel, InfosetInputter) to parse
the data and get the infoset representation from the InfosetOutputter. Since
2.0.0.
{code}
I can't reproduce this on my machine, but it's reproducable in this TravisCI
build:
https://travis-ci.org/apache/incubator-daffodil/jobs/523539231
Might be an OracleJDK specific check? Or TravisCI just has a different java
version than I do. This does not seem to fail the build due to a bug in sbt not
detecting javadoc errors, and it looks like the javadoc is still generated, but
this should be resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)