Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6190

fuse-bxms-integ project dependencies contains very old dependencies on mvel, jb-ip-bom etc

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Blocker
    • None
    • None
    • Integration Pack
    • None
    • % %

    Description

      For the two tags on intpack based on BxMS 6.4.0 ER2[1], it contains very old dependencies on mvel and jb-ip-bom, and it would introduce more transitive dependencies which version isn't correct.
      For example: for Fuse6.2+BxMS 6.4, lots of missing dependencies are missing from product env which most of them doesn't make sense. because lots of them are very old and productized version has been produced for BxMS6.4. To see the massive missing deps, click https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/fuse-team-mead-6.3-fuse-integration/8/console

      I think the root cause is that jboss-fuse-parent bom contain lots of unproductized deps and when importing both of them, jboss-fuse-parent one override the jboss-integration-platform bom.
      In order to get a consistent and unique dependencies, my suggestion here is:
      1) put jboss-integration-platform-bom import in the front of jboss-fuse-parent import.
      Like:
      <dependency>

      • <groupId>org.jboss.fuse.bom</groupId>
      • <artifactId>jboss-fuse-parent</artifactId>
      • <version>${version.fuse}</version>
        + <groupId>org.jboss.integration-platform</groupId>
        + <artifactId>jboss-integration-platform-bom</artifactId>
        + <version>${version.org.jboss.integration-platform}</version>
        <type>pom</type>
        <scope>import</scope>
        </dependency>
        <dependency>
      • <groupId>org.jboss.integration-platform</groupId>
      • <artifactId>jboss-integration-platform-bom</artifactId>
      • <version>${version.org.jboss.integration-platform}</version>
        + <groupId>org.jboss.fuse.bom</groupId>
        + <artifactId>jboss-fuse-parent</artifactId>
        + <version>${version.fuse}</version>
        <type>pom</type>
        <scope>import</scope>
        2) Explicit exclude the multiple version for hardcoded one case by case, for example: in the tag for fuse-6.2 +bxms 6.4 switchyard-transform should exclude mvel to avoid mutiple version.

      How to reproduce:
      1)checkout the intpack tag
      2)update the version.org.jboss.jboss-integration-platform to 6.0.8.Final-redhat-2 (to match bxms 6.4 ER2)
      3) running mvn dependency:tree to check the dependency and make sure it use consistent dependencies and the latest productized one.

      There might be more cases like this.
      But at least we need fix this in order to product a sensible intpack.

      [1]
      Fuse 6.3 / BxMS 6.4 :
      https://docs.google.com/document/d/1mSYLeq4LcjFMuZszeOm8vY6NRehUq5RQqaKYE8VwMRM
      tag: fuse-bxms-integ-1.7.0.redhat-630006

      Fuse 6.2.1 / BxMS 6.4 :
      https://docs.google.com/document/d/1BbdxpMaPfZxMBIoKvpWWtlSl1wXdmo846dHXmUA2a9g
      tag: fuse-bxms-integ-1.6.0.redhat-621005

      Attachments

        Activity

          People

            tcunning@redhat.com Thomas Cunningham
            rzhang+1@redhat.com Cheng Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: