[
http://jira.codehaus.org/browse/MENFORCER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Asmann updated MENFORCER-89:
-----------------------------------
Attachment: test.zip
I finally was able to reproduce the problem!
If a project has a groupId that consists of variables (eg
"${parent.groupId}.${parent.artifactId}"), running the enforcer-plugin triggers
a download of the POM, which might not exist in the remote repository!
Running the project without the enforcer works like it should.
In the ZIP is a small project to reproduce the bug. In case you tested it
WITHOUT the enforcer and have run 'mvn install', you won't be able to reproduce
the bug again unless you delete the project from your local repository first!
> Plugin doesn't validate my current build, but the latest SNAPSHOT in the
> repository!
> ------------------------------------------------------------------------------------
>
> Key: MENFORCER-89
> URL: http://jira.codehaus.org/browse/MENFORCER-89
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0-beta-1
> Reporter: Roland Asmann
> Attachments: test.zip
>
>
> I've added the enforcer-plugin to my build today, but now my projects don't
> build anymore! The reason for that is that the enforcer-plugin is reporting
> missing versions (<requirePluginVersions />), although the versions are
> actually set!
> I've been checking what might be wrong and noticed that as soon as the plugin
> executes, it checks for updates for the project that is currently being
> built! In that case, the plugin is actually right, because the latest
> deployed snapshots have some unversioned plugins. However, shouldn't the
> plugin validate the project currently in the reactor?
--
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
