On 2021-06-17, Jaikiran Pai wrote: > The recently released EA version of JDK 17 has introduced a change in > the javadoc tool. Previously (JDK 8 all the way through JDK 16) used > to log certain messages from the javadoc tool to STDOUT. Our javadoc > task's implementation expects such messages of STDOUT. Starting this > JDK EA release the behaviour has changed in the javadoc tool and it > now logs those messages to STDERR. This change was discussed in the > OpenJDK mailing list[1] and it has been noted that this is an > intentional change in the tool.
Who could expect that build tools try to parse output when we've never provided a Java API to run a typical build task? Sorry. > So right now I don't have specific proposals for fixing this but just > a note that we will have to look into this one for the upcoming JDK 17 > release. I guess we can simply concatenate stderr and stdout and look for the "warnings" message there. This should work for every version of Java supported by Ant. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
