You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Palaga (JIRA)" <ji...@apache.org> on 2018/01/03 07:53:00 UTC
[jira] [Updated] (MPLUGIN-331) Check the existence of plugin.xml
rather than project packaging in PluginReport.canGenerateReport()
[ https://issues.apache.org/jira/browse/MPLUGIN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Palaga updated MPLUGIN-331:
---------------------------------
Summary: Check the existence of plugin.xml rather than project packaging in PluginReport.canGenerateReport() (was: Check the existence of plugin.xml rather than project packaging in )
> Check the existence of plugin.xml rather than project packaging in PluginReport.canGenerateReport()
> ---------------------------------------------------------------------------------------------------
>
> Key: MPLUGIN-331
> URL: https://issues.apache.org/jira/browse/MPLUGIN-331
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Plugin
> Reporter: Peter Palaga
>
> {{org.apache.maven.plugin.plugin.PluginReport.canGenerateReport()}} currently reads
> {code}
> return "maven-plugin".equals( project.getPackaging() );
> {code}
> I propose to change it to
> {code}
> return "maven-plugin".equals( project.getPackaging() )
> || "takari-maven-plugin".equals( project.getPackaging() );
> {code}
> so that also takari-maven-plugins are supported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)