Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2017712

Summary: Missing maven-shade-plugin in CentOS Stream 9
Product: Red Hat Enterprise Linux 9 Reporter: Sandro Bonazzola <sbonazzo>
Component: maven-shade-pluginAssignee: Severin Gehwolf <sgehwolf>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer
Target Milestone: rcKeywords: Regression
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-02 09:34:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1990767    

Description Sandro Bonazzola 2021-10-27 10:02:11 UTC
maven-shade-plugin is not available on CentOS Stream 9 repos despite it's built for it: https://kojihub.stream.centos.org/koji/buildinfo?buildID=11976

It was previously available in CentOS Stream 8: http://mirror.centos.org/centos/8-stream/PowerTools/x86_64/os/Packages/maven-shade-plugin-3.1.0-3.module_el8.5.0+922+9f7ad99e.noarch.rpm 

The package is needed by oVirt project for building java-client-kubevirt package.

Comment 2 Josh Boyer 2021-10-27 10:38:33 UTC
(In reply to Sandro Bonazzola from comment #0)
> maven-shade-plugin is not available on CentOS Stream 9 repos despite it's
> built for it: https://kojihub.stream.centos.org/koji/buildinfo?buildID=11976
> 
> It was previously available in CentOS Stream 8:
> http://mirror.centos.org/centos/8-stream/PowerTools/x86_64/os/Packages/maven-
> shade-plugin-3.1.0-3.module_el8.5.0+922+9f7ad99e.noarch.rpm 
> 
> The package is needed by oVirt project for building java-client-kubevirt
> package.

It's available in the CentOS Stream 9 buildroot, which is available in CBS for projects to use.  oVirt should be able to consume it from there if it's configured correctly.  There is no strict need for this to be shipped in a customer facing repository.

Comment 3 Sandro Bonazzola 2021-10-27 11:11:11 UTC
(In reply to Josh Boyer from comment #2)

> It's available in the CentOS Stream 9 buildroot, which is available in CBS
> for projects to use.  oVirt should be able to consume it from there if it's
> configured correctly.  There is no strict need for this to be shipped in a
> customer facing repository.

having it in a private build root is not going to help developers who needs to build / test locally.
Not having it in a public repo means we'll have to rebuild it in CentOS Virt SIG or on COPR to make it available to developers.
We can do that, it's just wasting time doubling the work and the maintenance cost.

Comment 4 Josh Boyer 2021-10-27 11:16:23 UTC
(In reply to Sandro Bonazzola from comment #3)
> (In reply to Josh Boyer from comment #2)
> 
> > It's available in the CentOS Stream 9 buildroot, which is available in CBS
> > for projects to use.  oVirt should be able to consume it from there if it's
> > configured correctly.  There is no strict need for this to be shipped in a
> > customer facing repository.
> 
> having it in a private build root is not going to help developers who needs
> to build / test locally.

It's not private.  Anyone can go to CentOS Stream 9 koji and download the packages.  The same is true for CentOS Stream 8.

> Not having it in a public repo means we'll have to rebuild it in CentOS Virt
> SIG or on COPR to make it available to developers.

I don't see why that is the case.

> We can do that, it's just wasting time doubling the work and the maintenance
> cost.

I don't see how there is any maintenance by oVirt required at all.  The package is available publicly and will continue to be so.

Comment 5 Severin Gehwolf 2021-11-02 09:34:45 UTC
I'm closing this as won't fix. There is no intention to actually ship this package into a repository as that changes maintenance properties significantly. Currently, maven-shade-plugin, isn't a *runtime* dependency for anything. As mentioned previously, the build can be consumed from the CentOS build root.