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

Use fuse-bom in camel-wildfly examples

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: fuse-7.1
    • Fix Version/s: fuse-7.3
    • Component/s: Fuse EAP
    • Labels:
      None
    • Sprint:
      Fuse 7.3 Sprint 40 - Dev #1

      Description

      Working on ENTESB-9222, I tried to refactor the camel-wildfly-examples and ... I was going to open this: https://github.com/wildfly-extras/wildfly-camel-examples/compare/5.2.x.redhat-7-1-x...nicolaferraro:5.2.x.redhat-7-1-x?expand=1. But it actually creates a cycle.

      wildfly-camel-examples will depend on redhat-fuse with that change (boms), but there's fuse-eap in the pipeline that needs the wildfly-camel-examples and redhat-fuse that depends on both fuse-eap and wildfly-camel-examples (https://github.com/jboss-fuse/redhat-fuse/blob/eaaa32f563a0bbefa5ef3a25e5105cf54193f916/pom.xml#L304-L316).

      Tom Cunningham, James Netherton do you know if we can break this cycle and remove https://github.com/jboss-fuse/redhat-fuse/blob/eaaa32f563a0bbefa5ef3a25e5105cf54193f916/pom.xml#L304-L316 ?

      If it's not safe or the change is too complex, we may also think to postpone changing the fuse-camel examples.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  thomas.diesler Thomas Diesler
                  Reporter:
                  nibbio84 Nicola Ferraro
                  Tester:
                  Lukáš Löwinger
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: