Details

    • Bug
    • Resolution: Done
    • Major
    • 2.6.0.Final
    • 2.6.0.Final
    • WebLogic -> EAP
    • None
    • Hide

      Run windup on jee-example-app; go to Migration Issues report and look at "WebLogic proprietary logging classes" and "WebLogic proprietary logger (NonCatalogLogger) – then step into the source report for any file with those issues.

      Show
      Run windup on jee-example-app; go to Migration Issues report and look at "WebLogic proprietary logging classes" and "WebLogic proprietary logger (NonCatalogLogger) – then step into the source report for any file with those issues.

    Description

      The rules added in 2.6 cause a lot of noisy extra hints where WebLogic logging classes are used.

      Two main issues:
      1) When "WebLogic proprietary logger (NonCatalogLogger)" triggers, "WebLogic proprietary logging classes" (more general) triggers in the same place.
      2) "WebLogic proprietary logging classes" triggers more than once on a line if the class is referenced more than once on that line. So a line that says "X myX = new X()" triggers once on the first X and again on the X().

      Attachments

        Activity

          People

            mnovotny@redhat.com Marek Novotny
            dansmit Dan Smith (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: