Bug 2204506

Summary:	Update maven from 3.8.1 to 3.8.6 or higher on rhel repos
Product:	Red Hat Enterprise Linux 8	Reporter:	Spolti <fspolti>
Component:	maven	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED MIGRATED	QA Contact:	RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	gv
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Rebase
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 14:29:51 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Spolti 2023-05-15 19:33:46 UTC

Description of problem:
It would be nice to have the maven 3.8.6 version available to install from rpm repositories.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 gv 2023-08-24 12:55:36 UTC

The latest version of maven available is now 3.8.5, but that version has at least one concurrency bug affecting our parallell builds of Vespa using the maven-enforcer-plugin. See e.g.
https://issues.apache.org/jira/browse/MNG-7455
https://issues.apache.org/jira/browse/MENFORCER-468

The newest versions are 3.8.8 and 3.9.4, while 3.8.5 is more than one year old.

It would be nice to have an upgraded package available to avoid workarounds, like the maven-wrapper, for a stable build.

Comment 2 RHEL Program Management 2023-09-20 14:28:16 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-20 14:29:51 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.