[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539009#comment-17539009
]
ASF GitHub Bot commented on MNG-7468:
-------------------------------------
cstamas commented on PR #741:
URL: https://github.com/apache/maven/pull/741#issuecomment-1130374884
> @cstamas
>
> * can plugin descriptor simply have empty list of parameters?
> * NEVER fail or don't check at all?
> * or check in DefaultMojoExecutionConfigurator?
* it can, if plugin does not declare any param?
* IMHO NEVER fail, as you have no idea what Mojo is up to, checking may just
cause extra noise (IF Mojo does something funky)
* unsure what to say here 😄
> Unsupported plugins parameters in configuration should be verified
> ------------------------------------------------------------------
>
> Key: MNG-7468
> URL: https://issues.apache.org/jira/browse/MNG-7468
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Currently we can provide any xml tags in plugin configuration even if plugin
> Mojo doesn't support specific parameters.
> eg we can have:
> {code:xml}
> <plugin>
> <artifactId>example-maven-plugin</artifactId>
> <version>1.1.1</version>
> <configuration>
> <xxx>zzzz</xxx>
> </configuration>
> </plugin>
> {code}
> With example configuration Mojo is executed without any warning.
> Simply if parameters is not supported - build should break with some of
> invalid plugin configuration exception ...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
