[
http://jira.codehaus.org/browse/MENFORCER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MENFORCER-57:
-------------------------------
Testcase included: yes
Affects Version/s: 1.0-alpha-4
Attachment: MENFORCER-57.zip
The problem only seems to occur when using a "relativePath" to the parent. The
attached zip contains an example. Just run "mvn install" from the root
directory or the "module1" directory.
> Enforcer does not resolve local parent pom
> ------------------------------------------
>
> Key: MENFORCER-57
> URL: http://jira.codehaus.org/browse/MENFORCER-57
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0-alpha-4
> Reporter: Paul Gier
> Assignee: Brian Fox
> Attachments: MENFORCER-57.zip
>
>
> I have a multi-module project where the plugin versions are defined in a
> parent pom using pluginManagement. The enforcer plugin goes to the
> repository to look for the parent pom instead of looking at the local parent.
> As a result, I get a warning about missing plugin versions even though the
> versions are defined in the local parent pom, just not in the repository
> parent pom.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
