[
https://jira.codehaus.org/browse/MENFORCER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph closed MENFORCER-207.
------------------------------------
Resolution: Not A Bug
Haaaa nevermind, this is me being stupid. Explanation for my misunderstanding:
* The version-less plugin I had in my setup was bound to the clean phase.
* Naturally, to try an detect the problem, I called for the clean phase and the
profile where the plugin is bound (tried w/ and w/o profile)
* The enforcer plugin, on the other hand is bound to the validate phase of the
default lifecycle.
* I only just realized that executing the clean lifecycle does _not_ execute
the validate phase !
> requirePluginVersions does not apply when plugin defined in parent or profile
> ?
> -------------------------------------------------------------------------------
>
> Key: MENFORCER-207
> URL: https://jira.codehaus.org/browse/MENFORCER-207
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Grégory Joseph
>
> I see two cases where the rule doesn't seem to be applied:
> * a version-less plugin is declared in a parent pom outside the current
> reactor (for the sake of the exercise, the parent pom is released with
> -Denforcer.skip)
> * a version-less plugin is declared in a profile of the parent pom; the
> profile is activated in the child pom.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
