You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Roland Asmann (JIRA)" <ji...@codehaus.org> on 2010/01/17 01:44:55 UTC
[jira] Created: (MENFORCER-89) Plugin doesn't validate my current
build, but the latest SNAPSHOT in the repository!
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
[jira] Commented: (MENFORCER-89) Plugin doesn't validate my current
build, but the latest SNAPSHOT in the repository!
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MENFORCER-89) Plugin doesn't validate my current
build, but the latest SNAPSHOT in the repository!
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207183#action_207183 ]
Dan Tran commented on MENFORCER-89:
-----------------------------------
you may want to submit a producible pom, otherwise, this issue may may never get looked at
> 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
[jira] Commented: (MENFORCER-89) Plugin doesn't validate my current
build, but the latest SNAPSHOT in the repository!
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MENFORCER-89) Plugin doesn't validate my current
build, but the latest SNAPSHOT in the repository!
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ 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