You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/01/07 20:25:00 UTC

[jira] [Updated] (MENFORCER-455) New Enforcer API

     [ https://issues.apache.org/jira/browse/MENFORCER-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Slawomir Jaranowski updated MENFORCER-455:
------------------------------------------
    Component/s: Rule API

> New Enforcer API
> ----------------
>
>                 Key: MENFORCER-455
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-455
>             Project: Maven Enforcer Plugin
>          Issue Type: Improvement
>          Components: Rule API
>            Reporter: Slawomir Jaranowski
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.2.0
>
>
> Current Enforcer API was based on Maven/Plexus configuration, where each rule must be in the same package as plugin implementation.
> When rule is in another package user must provide implementation attribute on rule tag with full class name of rule.
> After MENFORCER-453 - we can implement rule as JSR 330 components.
> So package of rule will be not important.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)