RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

BuildRequires does not specify exact java version. On typical RHEL 7 java-1.8.0-openjdk is used in the end, but build fails.
If java-1.7.0-openjdk is used, build succeeds


Version-Release number of selected component (if applicable):
log4j-1.2.17-15.el7

How reproducible:
always

Steps to Reproduce:
1. install log4j srpm
2. yum-builddep log4j.spec
3. rpmbuild -ba log4j.spec

Actual results:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9:jar (default) on project log4j: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - /root/rpmbuild/BUILD/apache-log4j-1.2.17/src/main/java/org/apache/log4j/helpers/AppenderAttachableImpl.java:58: warning: no @param for event
[ERROR] int appendLoopOnAppenders(LoggingEvent event) {
[ERROR] ^
[ERROR] /root/rpmbuild/BUILD/apache-log4j-1.2.17/src/main/java/org/apache/log4j/helpers/AppenderAttachableImpl.java:58: warning: no @return
....
error: Bad exit status from /var/tmp/rpm-tmp.PlXhQt (%build)


Expected results:
...
+ exit 0

Additional info:

You can pass --disable-doclint to javadoc to workaround this.

Known issue. Exactly the same problem affects hundreds of other packages too. Theoretically this fixable, but would require a lot of work for little or no benefit.

I recall you had a hook in maven (ant?) which was disabling doclint by default, haven't you?

In Fedora, not in RHEL.

Java packages in RHEL 7 were built with OpenJDK 7. Building them with any other JDK was not tested - some builds may fail for different reasons, some may succeed, but produce wrong results.

Yes. that is right thing to do. Still the packages should be kept building by jdk7. Lukas, how did this happen?

During our rebuild test on rhel-7.
"yum-builddep log4j.spec" installs java-1.8.0-openjdk-devel in dependency chain.

Per previous comments, building with OpenJDK >7 is not supported nor do we plan to update the packages to support this.