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

[patching] Changes in org.ops4j.pax.logging.cfg do not propagate to newer version

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1
    • Patching
    • None
    • % %
    • Hide

      1. install JBoss Fuse 6.2.0
      2. update org.ops4j.pax.logging.cfg file
      3. patch JBoss Fuse using steps in https://mojo.redhat.com/docs/DOC-1049758
      4. the file org.ops4j.pax.logging.cfg is updated to newer version, but the user changes are removed

      This issue can also occur when patching 6.2.1 with a rollup patch:

      1) Install JBoss Fuse 6.2.1
      2) Update org.ops4j.pax.logging.cfg file
      3) Apply rollup patch (R1, R2, or R3)
      4) User changes in org.ops4j.pax.logging.cfg are removed

      Show
      1. install JBoss Fuse 6.2.0 2. update org.ops4j.pax.logging.cfg file 3. patch JBoss Fuse using steps in https://mojo.redhat.com/docs/DOC-1049758 4. the file org.ops4j.pax.logging.cfg is updated to newer version, but the user changes are removed This issue can also occur when patching 6.2.1 with a rollup patch: 1) Install JBoss Fuse 6.2.1 2) Update org.ops4j.pax.logging.cfg file 3) Apply rollup patch (R1, R2, or R3) 4) User changes in org.ops4j.pax.logging.cfg are removed
    • Sprint 5 - towards ER2

      Updates to files as in org.ops4j.pax.logging.cfg do not propagate to newer version, when patching from 6.2.0. to 6.2.1. in standalone JBoss Fuse. The org.ops4j.pax.logging.cfg file is attached

        1. org.ops4j.pax.logging.base.txt
          2 kB
        2. org.ops4j.pax.logging.cfg
          3 kB
        3. org.ops4j.pax.logging.patched.txt
          3 kB
        4. org.ops4j.pax.logging.resolved.txt
          3 kB
        5. org.ops4j.pax.logging.resolved-better.txt
          3 kB
        6. org.ops4j.pax.logging.user.txt
          3 kB

            ggrzybek Grzegorz Grzybek
            tplevko@redhat.com Tomas Plevko
            Tomas Plevko Tomas Plevko
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: