[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539023#comment-17539023
]
ASF GitHub Bot commented on MNG-7468:
-------------------------------------
cstamas commented on PR #741:
URL: https://github.com/apache/maven/pull/741#issuecomment-1130413736
> * if plugin does not declare any param user should not provide any
configuration - true?
> * break build in 4.x according to issue comment - `It should issue a
warning in 3.9.0 and break in 4.0.0.` by @michael-o
> * idea to check in `DefaultMojoExecutionConfigurator` is to avoid noise if
author provide own configuration for plugin, so we will only check for
`standard` configuration
* nope: plugin could get it from PlexusXmlConfig manually
* NOPE: NEVER break a build due this IMHO, not even in 4.x (unless we change
how plugins are configured, but I doubt)
* ack
> 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)
