Bug 758739 - RichFaces BOM references jboss-parent redhat-1
Summary: RichFaces BOM references jboss-parent redhat-1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces
Version: 2.0.0.DR05
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 2.0.0.DR06
Assignee: Marek Novotny
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-30 16:03 UTC by Karel Piwko
Modified: 2012-04-05 13:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-05 13:48:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP-7632 0 None Closed jboss-parent contains dependencyManagement sections 2012-07-04 17:24:48 UTC
Red Hat Issue Tracker RF-11760 0 None Resolved Remove parent section from richfaces-bom 2012-07-04 17:24:47 UTC

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).


Note You need to log in before you can comment on or make changes to this bug.