[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538133#comment-17538133
]
Tamás Cservenák edited comment on MNG-7468 at 5/17/22 11:52 AM:
----------------------------------------------------------------
IMHO, it should _always warn only_ as you cannot tell what mojo does... for
example, it could get MojoExecution injected and tamper directly with it's own
config even... For sure not fail the build, as that would be a breaking and
unwanted change: Maven was always "forgiving" with misconstructed/wrong but
parseable XML configuration...
was (Author: cstamas):
IMHO, it should _always warn only_ as you cannot tell what mojo does... for
example, it could get MojoExecution injected and tamper directly with it's own
config even...
> 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)
