Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55745

Migrate from analysis-core to warnings-ng

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      This plugin currently depends on Static Analysis Utilities, which is EOL and replaced by Warnings Next Generation.

        Attachments

          Activity

          Hide
          sspringett Steve Springett added a comment -

          Yes, there are plans on doing this. I need to determine if I need to write a whole plugin (similar to how it's done now) or if I can simply contribute a parser.

           

          I've iterated with the author numerous times over the past 6 months and I think everything is in place for us to do a proper plugin, but we'll see.

          Show
          sspringett Steve Springett added a comment - Yes, there are plans on doing this. I need to determine if I need to write a whole plugin (similar to how it's done now) or if I can simply contribute a parser.   I've iterated with the author numerous times over the past 6 months and I think everything is in place for us to do a proper plugin, but we'll see.
          Hide
          sspringett Steve Springett added a comment -

          I'm hoping to announce this when Dependency-Check 5.0 is GA (after it's milestones).

          Show
          sspringett Steve Springett added a comment - I'm hoping to announce this when Dependency-Check 5.0 is GA (after it's milestones).
          Hide
          sspringett Steve Springett added a comment -

          Migration to warnings-ng will no longer be performed. Refer to https://groups.google.com/forum/#!msg/dependency-check/2yMe6-Tg8tU/53SCfThcBQAJ

          Show
          sspringett Steve Springett added a comment - Migration to warnings-ng will no longer be performed. Refer to  https://groups.google.com/forum/#!msg/dependency-check/2yMe6-Tg8tU/53SCfThcBQAJ
          Hide
          jameshowe James Howe added a comment -

          Perhaps you should've linked the conversation here before deciding there weren't enough replies.

          As far as I can see, of the two responses, one wanted A1 (just the warnings-ng parser) and the other wanted B.
          I'm in the former camp, and just need the reporting capability, and would favour all reporting being integrated.
          If there's a parser for warnings-ng, then I probably have no need for a separate dependency-check plugin.

          Is it possible you could provide the parser for warnings-ng as well as your planned implementation of option B?
          I'm guessing, given your experience, you'd have the least trouble producing it quickly.

          Show
          jameshowe James Howe added a comment - Perhaps you should've linked the conversation here before deciding there weren't enough replies. As far as I can see, of the two responses, one wanted A1 (just the warnings-ng parser) and the other wanted B. I'm in the former camp, and just need the reporting capability, and would favour all reporting being integrated. If there's a parser for warnings-ng, then I probably have no need for a separate dependency-check plugin. Is it possible you could provide the parser for warnings-ng as well as your planned implementation of option B? I'm guessing, given your experience, you'd have the least trouble producing it quickly.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jameshowe James Howe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: