Bug 758739

Summary: RichFaces BOM references jboss-parent redhat-1
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Karel Piwko <kpiwko>
Component: RichFacesAssignee: Marek Novotny <mnovotny>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: high    
Version: 2.0.0.DR05CC: mnovotny
Target Milestone: ---   
Target Release: 2.0.0.DR06   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-05 13:48:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Piwko 2011-11-30 16:03:32 UTC 
Having <parent> element in the BOM file is fundamentally wrong.

If user imports dependencyManagement of the BOM file, it imports even the dependencies from its parent and upper ancestors. Since the ancestor is jboss-parent, it includes virtually the whole world.

Since jboss-parent:6-redhat-1 contains dependency management, it makes following usage broken, rendering bom file useless and destroying our usability efforts.


    <dependencyManagement>
        <dependencies>
                <dependency>
                <groupId>org.richfaces</groupId>
                <artifactId>richfaces-bom</artifactId>
                <type>pom</type>
                <scope>import</scope>
                <version>4.1.0-CR1-redhat-1</version>
                </dependency>            
        </dependencies>
    </dependencyManagement>
Comment 1 Marek Novotny 2011-12-08 20:41:22 UTC 
removed parent from richfaces-bom and also removed richfaces-bom from richfaces-root-parent
Comment 3 Karel Piwko 2012-04-05 13:48:20 UTC 
Verified in WFK 2.0.0.ER3 (a.k.a. 2.0.0.Beta1).