apache / apache/maven

[MNG-5563] Ensuring only the available parameters are allowed

Open
#6,765 5 comments 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
20h 42m
Merged PRs (30d)
297

Description

**[S. Ali Tokmen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alitokmen)** opened **[MNG-5563](https://issues.apache.org/jira/browse/MNG-5563?redirect=false)** and commented

I am one of the owners of Codehaus CARGO, which has a Maven2/Maven3 plugin; and would have an improvement request with regards to how parameters are managed.

Currently, what happens is that if a user unwillingly puts a parameter in the wrong place then the plugin execution continues as is. One of the latest such issues one of the users has had can be found on http://cargo.996258.n3.nabble.com/Maven-plugin-and-javaagent-tp18075.html

As an example, I can write the below POM and build still works (even thought the MOJO has no parameter called "foo"):

```

org.codehaus.cargo
cargo-maven2-plugin
1.4.6


bar

```

It would be good for the MOJO developer to be ablo instruct by MOJO to fail if there is an unknown parameter in the configuration.

---

**Remote Links:**
- [Page
](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65875544)

3 votes, 6 watchers

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.