You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/05/21 14:32:00 UTC
[jira] [Commented] (MENFORCER-384) Introduce Maven Enforcer
Extension
[ https://issues.apache.org/jira/browse/MENFORCER-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349296#comment-17349296 ]
Hudson commented on MENFORCER-384:
----------------------------------
Build failed in Jenkins: Maven » Maven TLP » maven-enforcer » master #54
See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/54/
> Introduce Maven Enforcer Extension
> ----------------------------------
>
> Key: MENFORCER-384
> URL: https://issues.apache.org/jira/browse/MENFORCER-384
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.0
>
>
> With MENFORCER-142 it was made possible to execute additional rules in case you couldn't touch the pom.
> This was done via a commandline property, but lacked the support for finegrained configuration as you can do with a plugin.
> The Maven Enforcer Extension does support this. It'll make use of the Maven extension mechanism, hooking into the build lifecycle.
> This extension will read its configuration from a predefined location, and will add these as new execution blocks to the buildplan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)