[
http://jira.codehaus.org/browse/MENFORCER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207215#action_207215
]
Roland Asmann commented on MENFORCER-89:
----------------------------------------
Okay, so I've been trying to create a simple little project to submit here, but
I can't reproduce it in a simple project. I'll keep on trying though.
I did however check all my other projects (running nightly builds in Hudson, so
that's easy enough) and there I noticed this problem occurs only on 2 of my
projects. I have no clue as to why, since at least 5 of them are similar in
structure and had missing versions in their previous iteration... Funny thing
is that in those other projects, the enforcer-plugin (or maven itself, I'm
still not sure which) doesn't even lookup the latest snapshot from the
repository. Like I said, it only does that in 2 projects and both of those then
fail.
For my builds, I can surely create a simple workaround (deploy a version
without the enforcer, but with the versions for plugins set) and then go on
from there, but I think this is a bug that definitely needs fixing!
So, that where I'm at at this point. As soon as I have a reproducible little
project, I'll attach it!
> 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
