maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Asmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MENFORCER-89) Plugin doesn't validate my current build, but the latest SNAPSHOT in the repository!
Date Sun, 17 Jan 2010 11:35:55 GMT

    [ http://jira.codehaus.org/browse/MENFORCER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207201#action_207201
] 

Roland Asmann commented on MENFORCER-89:
----------------------------------------

I'll rewrite one of my POMs for that... Although I think this problem occurs on any POM...

> 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
>
> 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

        

Mime
View raw message