apache / apache/maven-build-cache-extension
[MBUILDCACHE-126] [WARNING] Cannot find a Mojo parameter 'commandLineRules' to read for Mojo org.apache.maven.plugins:maven-enforcer-plugin:3.5.0:enforce {execution: enforce-maven}. This parameter should be ignored.
- Dominant language
- Java
- Stars
- 163
- Forks
- 77
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 4
Description
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** opened **[MBUILDCACHE-126](https://issues.apache.org/jira/browse/MBUILDCACHE-126?redirect=false)** and commented
When building my project using the Maven Build Cache Extension I get this output:
[INFO] — duplicate-finder:2.0.1:check (default) @ licensed-client —
[INFO] Ignoring POM project!
[WARNING] Cannot find a Mojo parameter 'commandLineRules' to read for Mojo org.apache.maven.plugins:maven-enforcer-plugin:3.5.0:enforce {execution: enforce-maven}. This parameter should be ignored.
I know that this issue came up in the past (MBUILDCACHE-56) but it is marked as fixed so I'm not sure why I'm getting this warning in version 1.2.0
Is this a regression or am I doing something wrong?
---
**Affects:** 1.2.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the warning with Maven Build Cache Extension 1.2.0, Maven Enforcer 3.5.0, and the enforce-maven execution described in the issue. Compare the behavior with MBUILDCACHE-56 and determine whether the commandLineRules warning is a regression or expected configuration behavior. Done means the cause is established and the warning is no longer incorrectly emitted, with a regression test if the project provides an applicable test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100