Uploaded image for project: 'Maven Plugin Tools'
  1. Maven Plugin Tools
  2. MPLUGIN-310

PluginReport should use generated plugin.xml by default

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.4
    • 3.5
    • Plugin Plugin
    • None

    Description

      Reading the descriptor from META-INF/maven/plugin.xml seems more efficient than (re)scanning all classes for mojos. And it could be an extra check it this file was generated correctly. So this file should be the input by default for reports. If it fails for some reason fall back to the original MojoScanner.

      Attachments

        Issue Links

          is depended upon by

          Task - A task that needs to be done. MPLUGIN-331 Check the existence of plugin.xml rather than project packaging in PluginReport.canGenerateReport()

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. MPLUGIN-294 'report' mojo should use 'extractors' configuration parameter

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            People

              rfscholte Robert Scholte
              rfscholte Robert Scholte
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: