[
https://issues.apache.org/jira/browse/MENFORCER-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911722#comment-17911722
]
ASF GitHub Bot commented on MENFORCER-516:
------------------------------------------
bpfoster opened a new pull request, #344:
URL: https://github.com/apache/maven-enforcer/pull/344
This will allow the enforcer to utilize rule configuration defined in the
project POM when the rule is run explicitly from the command line, e.g. `mvn
enforcer:enforce -Denforcer.rules=requireReleaseDeps`.
Following this checklist to help us incorporate your contribution quickly
and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MENFORCER) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MENFORCER-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> Honor rule configuration when invoked from the command line
> -----------------------------------------------------------
>
> Key: MENFORCER-516
> URL: https://issues.apache.org/jira/browse/MENFORCER-516
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Affects Versions: 3.5.0
> Reporter: Ben Foster
> Priority: Major
>
> I would like to configure a rule within the pom, and invoke just that rule
> from the command line, with the rule honoring the configuration in the pom.
>
> For example, if I configure the plugin in the pom like:
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-enforcer-plugin</artifactId>
> <version>3.5.0</version>
> <configuration>
> <rules>
> <requireReleaseDeps>
> <excludes>
> <exclude>my-project-group:*</exclude>
> </excludes>
> </requireReleaseDeps>
> </rules>
> </configuration>
> </plugin>{code}
>
> And run maven like:
> {code:java}
> $ mvn enforcer:enforce -Denforcer.rules=requireReleaseDeps {code}
>
> I would expect / like the exclude configuration to apply. Instead it does
> not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
