Bug 1789833

Summary:	maven-artifact-transfer for EPEL8
Product:	[Fedora] Fedora	Reporter:	lionel.cons
Component:	maven-artifact-transfer	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	decathorpe, java-sig-commits, mhroncok, mizdebsk, stewardship-sig
Target Milestone:	---
Target Release:	---
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:	2020-02-04 16:11:37 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:	1789677

Description lionel.cons 2020-01-10 14:23:11 UTC

java-dirq requires maven-javadoc-plugin to be compiled on CentOS/RHEL 8 through EPEL. See #1789677.

maven-javadoc-plugin requires maven-artifact-transfer which is not yet in EPEL8.

Could you please make maven-artifact-transfer available on EPEL8?

Comment 1 Miro Hrončok 2020-01-12 19:03:22 UTC

Do you want to maintain the package in EPEL 8? (Or in Fedora and EPEL?) This package is maintained by the Stewardship SIG: https://fedoraproject.org/wiki/SIGs/Stewardship -- the group doesn't generally maintain packages in EPEL.

Comment 2 lionel.cons 2020-01-13 07:03:28 UTC

Thanks for the offer but I do not want to maintain maven-artifact-transfer on EPEL8.

Note that my package (java-dirq) has now been built on EPEL8. maven-artifact-transfer (like maven-javadoc-plugin) is still nice to have on EPEL8 but it is not blocking me anymore.

Comment 3 Miro Hrončok 2020-02-04 16:11:37 UTC

Whoever would like to maintain this package in EPEL 8, feel free to reopen this bug.