#2040 Determine supported javadoc options
Closed: Fixed None Opened 8 years ago by mharmsen.

Javadoc 1.8 introduced the mandatory use of 'doclint', and while beneficial in identifying javadoc errors, it subsequently broke hundreds of javadoc text in the PKI project By default, since javadoc documentation is produced during compilation of the project, this resulted in an inability to successfully compile the PKI source.

Fortunately, as documented in Turning off doclint in JDK 8 Javadoc, the javadoc option "-Xdoclint:none" was introduced into the 'CMakeLists.txt' file in order to prevent this new default javadoc behaviour until such time as these javadoc errors can be fixed.

Unfortunately, the introduction of this new javadoc option is incompatible with Javadoc 1.7, and consequently causes compilation to fail on systems utilizing this option.

Although checks were inserted into the CMakeLists.txt file to address this problem, they were based upon the compiling machines specified version of 'Java', and this was found to be problematic when the specified version of 'Javac' differs from the specified version of 'Java'.

Since the version of 'Javadoc' should be associated with the specified version of 'Javac' instead of the specified version of 'Java', this check must be changed accordingly.


Checked into DOGTAG_10_2_5_RHEL_BRANCH:

commit d93ad25d3c954fcb73637795ccdcba04aad6e810
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Feb 18 17:56:32 2016 -0700

    Fix to determine supported javadoc options (spec file change)

    - PKI TRAC Ticket #2040 - Determine supported javadoc options

commit db7055457d421b796c1af6f0549a746a65939a05
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Feb 18 17:53:26 2016 -0700

    Fix to determine supported javadoc options

    - PKI TRAC Ticket #2040 - Determine supported javadoc options

Checked into 'master': c32dd90ef638e9653136eeb901426c56b511fda4

Checked into 'DOGTAG_10_2_BRANCH': 134d62bd45389979af8d06002b348599b8757b74

Checked into 'DOGTAG_10_2_6_BRANCH': 5763b6d5da785c6c5dbf696fc927cf90140a0613

Checked into DOGTAG_10_2_RHEL_BRANCH:

commit a45d3c4146c56f589cca292604e79ef4c2fc69d5
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Feb 18 17:53:26 2016 -0700

    Fix to determine supported javadoc options

    - PKI TRAC Ticket #2040 - Determine supported javadoc options

    (cherry picked from commit db7055457d421b796c1af6f0549a746a65939a05)

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.3.0.a1

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2328

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata