apache / apache/maven-enforcer
[MENFORCER-433] Add rule to ban property
- Dominant language
- Java
- Stars
- 161
- Forks
- 180
- Avg merge
- 1d 20m
- Merged PRs (30d)
- 8
Description
**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MENFORCER-433](https://issues.apache.org/jira/browse/MENFORCER-433?redirect=false)** and commented
Similar to `requireProperty` there should be a `banProperty` which ensures that a property with a specific name is not set at all.
This is useful in case a property is no longer supported for profile activation, or to enforce that e.g. the settings.xml does not contain a certain element.
---
1 votes, 1 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing `requireProperty` rule and its tests in the Maven Enforcer plugin. Add the corresponding `banProperty` behavior so a named property being set fails validation while an absent property passes, then extend the related tests to cover both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100