Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-11490

Typo in deprecation warning when adding a deprecated property resource on JGroups protocol

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Trivial
    • 7.1.0.ER2
    • 7.1.0.ER1
    • Clustering
    • None

    Description

      See https://issues.jboss.org/browse/JBEAP-11190?focusedCommentId=13419465&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13419465, point #4.

      There's a typo in the deprecation warning - missing space. Look for operationto [1].

      Operation add against the resource at address /subsystem=jgroups/stack=udp/protocol=org.jgroups.protocols.AUTH/property=auth_class is deprecated, and it might be removed in future version. See the the output of the read-operation-description ***operationto*** learn more about the deprecation.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2971 Typo in deprecation warning when adding a deprecated property resource on JGroups protocol

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11466 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta28

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11190 JGroups backward compatibility issues

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              rpelisse@redhat.com Romain Pelisse
              rjanik@redhat.com Richard Janik
              Richard Janik Richard Janik
              Richard Janik Richard Janik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: