Bug 1348595

Summary:	Installing rh-java-common-scldevel installs entire maven30 collection
Product:	Red Hat Software Collections	Reporter:	Severin Gehwolf <sgehwolf>
Component:	rh-maven35	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED ERRATA	QA Contact:	Jan Kepler <jkejda>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rh-maven35	CC:	jkejda, mizdebsk
Target Milestone:	alpha
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rh-maven35-1-1.1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-24 09:53:38 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:	1448496

Description Severin Gehwolf 2016-06-21 14:24:45 UTC

Description of problem:
When rh-java-common-scldevel gets installed (e.g. to get access to scl_prefix_java_common macro) the entire maven30 collection seems to get installed as well.

Version-Release number of selected component (if applicable):
rh-java-common-scldevel-1.1-46.el7

How reproducible:
100%

Steps to Reproduce:
1. $ yum install rh-java-common-scldevel

Actual results:
All, or most?, maven30 packages get installed. This includes maven itself and xmvn.

Expected results:
rh-java-common-scldevel and perhaps rh-java-common-runtime gets installed, but not the entire maven30 collection.

Additional info:
See also bug 1348582. Consider a collection which has a BR dep on rh-java-common-scldevel and rh-maven33-scldevel. This would drag in both collections, maven30 and rh-maven33. This can't be right.

Comment 6 errata-xmlrpc 2017-10-24 09:53:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3022