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

Investigate how to build/ship subset of extensions

    XMLWordPrintable

Details

    • False
    • False
    • % %
    • ?
    • 0
    • 0% 0%
    • Todo
    • Undefined

    Description

      Right now we build and ship everything in Camel from upstream even though we don't support every component/extension/kamelet. While we could modify our downstream POMs across Camel 3, Camel Quarkus, Camel-K to exclude some modules, this approach isn't easily portable across releases. Ideally we would have a configurable way to exclude certain modules. Upstream such a property would be empty and downstream we could fill it with modules we don't wish to support (yet).

      Attachments

        Issue Links

          Activity

            People

              gnodet@redhat.com Guillaume Nodet (Inactive)
              janstey@redhat.com Jonathan Anstey
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: