[
https://issues.apache.org/jira/browse/MENFORCER-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702286#comment-17702286
]
Slawomir Jaranowski commented on MENFORCER-475:
-----------------------------------------------
[~delany] - Does issue also exist with Maven 3.x? - if no I will assume rather
bug in Maven 4.x
As always simple example project will be appreciated.
> Only evaluate after aggregating pluginManagement
> ------------------------------------------------
>
> Key: MENFORCER-475
> URL: https://issues.apache.org/jira/browse/MENFORCER-475
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: requirePluginVersions
> Affects Versions: 3.2.1
> Reporter: Delany
> Priority: Major
>
> The rule fails if a plugin is configured in 2 pluginManagement sections (one
> of which is in a profile), and the profile's pluginManagement does not
> configure a plugin version.
> Profiles are often used to augment the existing configuration for a plugin,
> so there's no need to repeat the version number.
> However if the profile is introducing the plugin to the build, then a version
> tag should be required.
> The rule should evaluate whether a version number has been set after
> aggregating the configurations and resolving the profiles.
> This is a new issue from Maven 4.0.0-alpha-5
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
