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

Remove/disable unsupported fabric8 artifacts from product branches for FIS2.0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • FIS 2.0
    • FIS 2.0
    • FIS-Fabric8
    • None
    • % %
    • FIS 2.0 Sprint 5

      FIS 1.0 contained the following artifacts.. (including their origin fabric8 github repository)

      # FIS 1.0 artifacts (not including BOMs, POMs and examples)
      
      fabric8io/kubernetes-client openshift-client
      fabric8io/kubernetes-client openshift-mock
      fabric8io/kubernetes-client kubernetes-mock
      fabric8io/kubernetes-client kubernetes-model
      fabric8io/kubernetes-client kubernetes-karaf
      fabric8io/kubernetes-client kubernetes-client
      
      fabric8io/kubernetes-model kubernetes-model-annotator
      fabric8io/kubernetes-model kubernetes-model-generator
      
      fabric8io/fabric8 fabric8-annotations
      fabric8io/fabric8 fabric8-arquillian
      fabric8io/fabric8 fabric8-cdi
      fabric8io/fabric8 fabric8-maven-plugin
      fabric8io/fabric8 fabric8-utils
      fabric8io/fabric8 hawt-app-maven-plugin
      fabric8io/fabric8 jolokia-assertions
      fabric8io/fabric8 kubernetes-api
      fabric8io/fabric8 kubernetes-assertions
      fabric8io/fabric8 kubernetes-generator
      fabric8io/fabric8 kubernetes-jolokia
      
      fabric8io/fabric8-ipaas.git mq-client
      fabric8io/fabric8-ipaas.git camel-amq
      
      

      Currently the redhat-fis-2_0 branches in these github repos contain all of these + the original upstream components, of which not all should be shipped with FIS 2.0.

      Please explicitly state which components should be added to FIS for 2.0 (presumably due to some iPaaS requirement) and remove the rest from the FIS 2.0 product branches.

      See also https://issues.jboss.org/browse/OSFUSE-100

              Unassigned Unassigned
              maschmid@redhat.com Marek Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: