Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-9300

DeltaSpike container control dependency in Camel CDI should be optional

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.16.0
    • Fix Version/s: 2.16.1, 2.17.0
    • Component/s: camel-cdi
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      DeltaSpike container control API is only used to bootstrap Camel CDI in Java SE either directly with the Main class or via the Camel Maven plugin. Hence that dependency should be declared optional so that dependent projects that uses Camel CDI in non SE environments do not have to deal with it. This is the case of WildFly Camel for example. Note that the DeltaSpike container control packages are already excluded form OSGi imports.

      As the Camel Maven plugin does not check for optionality when adding CDI extra plugin dependencies (when useCDI is set to true), it is safe to declare that dependency optional.

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              antonin.stefanutti Antonin Stefanutti
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: