axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Schöning (JIRA) <>
Subject [jira] [Updated] (AXIS2-5885) Generating apidocs fails with Java 8.
Date Fri, 08 Sep 2017 07:13:00 GMT


Thorsten Schöning updated AXIS2-5885:
    Attachment: AXIS2-5885 01.patch
                AXIS2-5885 02.patch

I started to have a look at the individual errors Javadoc is complaining about and startet
to fix at least some of them to get a feeling on how many errors Javadoc will complain about
at all. Seems to be multiple hundreds, because it aborts with 100 errors/warnings always,
even after I fixed dozens of those. And I'm pretty sure I did because I verified that the
lines Javadoc was complaining about before were gone after I fixed those. It's always different
lines with errors.

I'll attach what I've changed so far to not let it be a waste of time, but it seems it's too
much to fix at once.

Two choices here: If "failOnError" is applied, build will succeed, but it's pretty likely
that no one will ever fix all the remaining issues. If "failOnError" is not applied, pressure
to fix the underlying problems will be there and maybe some people will correspond some fixes
over time until everything is solved. But most likely they will only apply "failOnError" on
their own? :-)

> Generating apidocs fails with Java 8.
> -------------------------------------
>                 Key: AXIS2-5885
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 1.8.0
>         Environment: Windows 10 x86-64, JDK 1.8
>            Reporter: Thorsten Schöning
>            Priority: Minor
>         Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
> The project "apidocs" can not be build by default using Java 8 because of a lot of errors
in the Javadocs and the new "javadoc" errors on those problems instead of warning/ignoring
them. A workaround is to add "<failOnError>false</failOnError>" to the configuration,
in that case the errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs to fix what
and where "javadoc" says. But some errors are related to missing packages and might be a hint
to classpath issues or some problems with available packages in the build?
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\
error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\
warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {CODE}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message