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.
Bug 1980980 - jaxb-stax-ex: FTBFS with junit-related errors
Summary: jaxb-stax-ex: FTBFS with junit-related errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: jaxb-stax-ex
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: beta
: ---
Assignee: RHCS Maintainers
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-10 10:09 UTC by Florian Weimer
Modified: 2021-10-07 02:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-28 09:38:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Florian Weimer 2021-07-10 10:09:56 UTC 
A rebuild of jaxb-stax-ex-1.8.3-3.el9 failed with these errors:

[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ stax-ex ---
[WARNING] Can't extract module name from junit.jar: null
[WARNING] Can't extract module name from test-classes: null
[WARNING] Can't extract module name from hamcrest.jar: null
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[INFO] Compiling 2 source files to /builddir/build/BUILD/jaxb-stax-ex-1.8.3/target/test-classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /builddir/build/BUILD/jaxb-stax-ex-1.8.3/src/test/java/org/jvnet/staxex/util/ByteCodeVersionTest.java:[16,17] package org.junit does not exist
[ERROR] /builddir/build/BUILD/jaxb-stax-ex-1.8.3/src/test/java/org/jvnet/staxex/util/ByteCodeVersionTest.java:[17,17] package org.junit does not exist
[ERROR] /builddir/build/BUILD/jaxb-stax-ex-1.8.3/src/test/java/org/jvnet/staxex/util/XMLStreamReaderToXMLStreamWriterTest.java:[25,17] package org.junit does not exist
[ERROR] /builddir/build/BUILD/jaxb-stax-ex-1.8.3/src/test/java/org/jvnet/staxex/util/ByteCodeVersionTest.java:[28,6] cannot find symbol
  symbol:   class Test
  location: class org.jvnet.staxex.util.ByteCodeVersionTest
Comment 1 Endi Sukma Dewata 2021-08-11 17:55:17 UTC 
Mikolaj, any idea how to fix this?
Note You need to log in before you can comment on or make changes to this bug.