You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/08/11 22:08:20 UTC

[jira] [Commented] (MPLUGIN-310) PluginReport should use generated plugin.xml by default

    [ https://issues.apache.org/jira/browse/MPLUGIN-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418027#comment-15418027 ] 

Hudson commented on MPLUGIN-310:
--------------------------------

SUCCESS: Integrated in maven-plugin-tools #262 (See [https://builds.apache.org/job/maven-plugin-tools/262/])
[MPLUGIN-310] PluginReport should use generated plugin.xml by default (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1756054])
* maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java


> PluginReport should use generated plugin.xml by default
> -------------------------------------------------------
>
>                 Key: MPLUGIN-310
>                 URL: https://issues.apache.org/jira/browse/MPLUGIN-310
>             Project: Maven Plugin Tools
>          Issue Type: Bug
>          Components: Plugin Plugin
>    Affects Versions: 3.4
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 3.5
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)