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

[Patch mechanism] Patch:list command doesn't make sense in fabric environment

    XMLWordPrintable

Details

    • % %
    • Hide
      1. create fabric
      2. install the patching mechanism for build nr. 69, using steps provided in : https://mojo.redhat.com/docs/DOC-1049758 (Patch is applied to version 1.1 but not used)
      3. use patch:list command
      Show
      create fabric install the patching mechanism for build nr. 69, using steps provided in : https://mojo.redhat.com/docs/DOC-1049758 (Patch is applied to version 1.1 but not used) use patch:list command

    Description

      It is not really a blocker but more like enhancement to the patch mechanism. When adding patch to the fabric environment using the patch:add command that was used previously in standalone mode, you get this output.

      JBossFuse:karaf@root> patch:add file:/home/fuse/jboss-fuse-full-6.2.1.redhat-070.zip
      [name]                                   [installed] [description]
      jboss-fuse-full-6.2.1.redhat-070         false       jboss-fuse-full-6.2.1.redhat-070
      

      Then if you continue with patching process the installed tag is always set to false. The command patch:fabric-install doesn't change this tag nor upgrading some container to a version with applied patch.

      In my opinion it would be better to track name of the version with applied patch or discard this output and patch:list command when fabric is created if it is possible. At the moment this information is misleading.

      Attachments

        Issue Links

          Activity

            People

              ggrzybek Grzegorz Grzybek
              rjakubco Roman Jakubco (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: