Bug 899617 (JBPAPP6-13)

Bugzilla References: Added: https://bugzilla.redhat.com/show_bug.cgi?id=758739

Linking Richfaces specific issue

Link: Added: This issue relates to RF-11760

Bugzilla References: Removed: https://bugzilla.redhat.com/show_bug.cgi?id=758739 Added: https://bugzilla.redhat.com/show_bug.cgi?id=758739

I believe the reason we put dependencyManagement into the parent is to control the versions of all EAP related project builds.  It seems like you would want this even for non-EAP product builds.

What is the problem with importing the dependencyManagement information?  This wouldn't have any effect on the classpath, it just forces you to use the correct versions of any eap dependencies.

I have problems with using richfaces-bom in the dependency managemement.
See following example:

{code:xml}
    <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>
{code}

I have following dependencies in the example which I don't want to be overridden:

{code:xml}
<dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-entitymanager</artifactId>
            <version>3.5.0-Final</version> <!-- not possible, will be overridden to 4.0.x -->
</dependency>

<dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>1.5.8</version> <!-- not possible, will be overridden to 1.6.x -->
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-test</artifactId>
            <scope>test</scope>
            <version>3.0.6.RELEASE</version> <!-- not possible, will be overridden to 2.5.6.x -->
        </dependency>
        ... 
{code}

As you can see, users using richfaces-bom:4.1.0-CR1-redhat-1 will won't get Richfaces dependencies only but he will get even Hibernate, Hibernate Validator, Spring!, basically everything from jboss-dependency-management-eap and jboss-dependency-management-build.

This is definitely not desired. Richfaces-bom uses jboss-parent to have the same plugin versions for deployment and release, for instance. In the community it does not matter, as community version have no dependencyManagement. However, productized version of jboss-parent has a dependencyManagement and therefore it becomes a part of richfaces-bom.

Linked richfaces issue is about making bom file independent of jboss-parent. However, following issue will affect any project which defines a *consumable bom* which has jboss-parent somethere. Might it be Hibernate Search or something from EDG, SOA, etc. next time.

Attached a diagram to illustrate the problem

Attachment: Added: eap-vs-community.pdf

Marek Novotny <mnovotny> changed the Status of [bug 758739|https://bugzilla.redhat.com/show_bug.cgi?id=758739] from NEW to ON_DEV

Marek Novotny <mnovotny> made a comment on [bug 758739|https://bugzilla.redhat.com/show_bug.cgi?id=758739]

removed parent from richfaces-bom and also removed richfaces-bom from richfaces-root-parent

Marek Novotny <mnovotny> changed the Status of [bug 758739|https://bugzilla.redhat.com/show_bug.cgi?id=758739] from ON_DEV to ON_QA

Removed the dependency management from the jboss-parent in [e4ffe797|http://git.app.eng.bos.redhat.com/?p=jboss/jboss-parent-pom.git;a=commit;h=e4ffe797b898127182fefe7e06d7cd43168d7dd8].
Unfortunately, this change will make a lot of our current POMs invalid, but we will gradually fix them.

Because of the effect this has on breaking the builds, we decided to revert the jboss-parent version 6-redhat-1, and create a new jboss-parent with an updated version: JBPAPP-7773

Link: Added: This issue relates to JBPAPP-7773

Link: Added: This issue is related to JBPAPP-7913

Docs QE Status: Removed: NEW 

Fixing Affects and Fix in Version